parseBlock, steps of compiling

[Paul Dufresne]

>You're overthinking this entirely too much. freeVariables just points
>out which variables from other the parent environments the block is
>using - nothing more, nothing less! It doesn't store any state at all,
>nor should it, nor was it meant to.

Oh! Then I think you can ignore my message about methods having no memory.

BUT STILL parseBlock should have a local variable, let's say returnedBlock, 
distinct from
the input variable block, it's 'lexical parent'.

Ok, so it just means that although the block A defined in B can be pass as 
an input variable to
a block C defined in D, A used in C, access the environment defined in B.

_________________________________________________________________
MSN Messenger : discutez en direct avec vos amis !  
http://messenger.fr.msn.ca/