7500+ entries in 0.013s
mod6: Yup, sounds good jurov. Thanks!
mod6: Ready to have a nice evening out with a picnic.
mod6: mircea_popescu: makes sense. sounds like you're prepared.
mod6: i lul'd about the food in the icebox.
mod6: nice pics of the beach.
mod6: let's see if he can up himself here... standby
mod6: yeah, we got his irc set up, so thats his nick now. got his key in, so that's good.
mod6: what does 'P' stand for when you say "FZ_OddP" or "FZ_EvenP" ... etc? Parameter?
☟︎ mod6: Here's a dumb question...
mod6: i'm probably getting ahead of myself though. was just saying "*thumbs-up*" on comments.
mod6: perhaps -- i certainly think it's good to link l0gz in footnotes or whatnot. the what/why/how doc aught to summarize all of thinking/decision making that went into the code.
mod6: but the comments I've seen in there are helpful, as long as they are accurate.
mod6: and ya, that's what i mean, more or less. what/why/how type of explanations.
mod6: i do also think there could be paragraphs even written around certain procedures in ffa. but not sure if that belongs in the code, or as a corresponding document outside of the code.
mod6: asciilifeform: i like the added comments in there. keep it up.
mod6: please do keep reporting such irregularities though.
mod6: ohmahgerd, it's alive
mod6: i know you're pretty swamped -- when you're comfortable with deedbots changes, etc. you know.
mod6: and please do send 'em my way when you have time
mod6: trinque: i didn't say we /should/ add more classes.
mod6: Submit me a vpatch, Sir.
mod6: I dunno about perma-banned, but I do see what you mean by that trinque, in this specific case.
mod6: ah yeah, i do have a rawtx on sitting here -- just needs testing. also, still have some makefile changes that are needing some testing/review. and further, want to put in some requested changes to import/dump priv key.
mod6: iirc I had created a proper vpatch of the thing last year, but we never wrapped up all the testing. i'd like to revisit that.
mod6: speaking of trinque's usage of polarbeard's rawtx vpatch -- im planning to get deeper into that this month.
mod6: mircea_popescu: aha, indeed Sir.
mod6: mircea_popescu: understood. it is more a learning process than anything at this point.
mod6: anyway, i don't wanna be a distraction. am simply, hopefully, on a useful side-quest.
mod6: asciilifeform: sure. makes sense.
mod6: it adds so much to the history though. being able to see wtf we were talking about.
mod6: <+asciilifeform> so there has to be a synthetic (i.e. Unsigned_32 ) type , that on archs that have narrower bitness than that, ends up a doubleword << ah, i see.
mod6: unless you wanna give me access to your drive
mod6: and Framedragger came along and did that handy thing and archived all that stuff. really, can't live without that bot.
mod6: see... i thought so too.. because yesterday i was digging up our conversation from august of '15 where we were looking at gnupg -- that night we had like 69 pastes.
mod6: The hope here is... when these changes are made, the given inputs still match the expected outputs.
mod6: a way of doing necessary work, and forcing myself to do the maff at the same time.
mod6: ANNND. hopefully will grok moar as well.
mod6: that's the aim anyway. but, yah, might find something along the way too.
mod6: aha, this indeed may be the case - something found. but the main interest "does it do what it ~should~ do, given these inputs"
mod6: to understand the thing, one can simply do the: B ^ ((S - 1) & (A ^ B)) on a calc
mod6: the fz_mux wasn't too bad, etc.
mod6: we'll see how hairy it gets :]
mod6: well, they're hopefully clear enough to be understood.
mod6: so, that's what I'm spending time on now anyway. and, making good progress in a short amount of time. however, ya, many gaps i msure.
mod6: i believe there to be a lot of merit to having unit tests around the specific procedures and functions in ffa.
mod6: that's more of a higher-level, functional style test.
mod6: probably won't even start until we're closer to a finalized version of ffa.
mod6: once we have some solid unit tests in place, i'll look at some functional tests as a higher-level way to ensure we don't regress as well. but that's a bit later yet.
mod6: again, these are unit tests, not functional, integration, or performance tests. meaning: i simply call a (so far public) procedure/function within ffa with specific parameters, and expect specific outputs.
mod6: im certain that even the tests that I do have are missing certain cases -- but its a starting point. and when I publish these, the hope is that people here can help fill in the gaps of the coverage so we can use this as a means to ensure that we do not regress as changes occur to the code.
mod6: i hope to glean some deeper understanding of the secret shifting from these tests as well.
mod6: im hoping to get some tests around the shifting procedures possibly today or this weekend. alf's latest changes from yesterday would fit into that as well.
mod6: i don't have a ton of coverage yet -- just mainly around the fz bitwise ops, fz_add, fz_mult, handfull of others.
mod6: ive been writing unit test for ffa
mod6: how you doin' shinohai?
mod6: we've gotta have that.
mod6: that's a mighty useful feature too btw.
mod6: I did, but i took mine down a while ago.
mod6: Thanks pete_dushenski!
mod6: Updated Republican Node List with pete_dushenski's new '199.204.187.186'.
mod6: seems like a hockey guy
mod6: pete_dushenski: re qntra shares, thx!