On Mon, 31 Dec 2007 12:26:06 -0500 Slava Pestov <[EMAIL PROTECTED]> wrote:
> Sorry I'm late to the party guys, my net access is sporadic here. > <snip> > > As a programmer it tends to not matter how things are, so long as they > > are explained clearly and I get a decent reason that doesn't make me > > scream "bullshit". If the rule's #2 then that's the rule, but I > > haven't seen any "standard stack protocol design guide" yet. > > > Let's write one :-) Also, check out > http://www.cs.rit.edu/usr/local/doc/gforth/Designing-the-stack-effect-Tutorial.html#Designing%20the%20stack%20effect%20Tutorial So, I'm inspired to write this, but I'll need some help. First off, this is an awesome kind of clustering of the concepts behind an API: http://hackety.org/2007/10/31/theEntiretyOfTheShoesFamily.html Sure, it's in why's style of pictures, but that's what I think I'll write. Second, someone mentioned that you need 50 words to be proficient in Factor. Alright, can people pitch in a list of those 50, and maybe a loose categorization of them? I'll then take the time to document them and see what comes out. Third, a list of the 10 most important idioms to start studying would be the bridge to the next part. Thanks! -- Zed A. Shaw - Hate: http://savingtheinternetwithhate.com/ - Good: http://www.zedshaw.com/ - Evil: http://yearofevil.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
