Thank you for your responses, Christopher & Geir. I get the picture : the side effects I pointed out are the problematic side of a volontary implementation choice... (and all implementation choices are by definition always somewhere between a bug and a feature... ;-) ).
> > Why not make context.localscope true? What's the problem there? > - it's a global parameter change for a local problematic - all needed global stuff must be passed as arguments to macros - and what if, after all, I want the global context to be changed sometimes ? In fact, to summerize, we have no call stack (hence, no recursion stack) inside macros when localscope is false : reference resolution is done in the flat world of inlining, and retrospectively It looks quite homogenic to do so. Chirstopher's #local directive proposal looks quite right to me, and I volunteers to write it. But (supposing my code is ok), will it be incorporated as a new functionnality ? A patch has a quite short lifetime... Time for what, now, votes, or validation, or something ? Thanx, CloD -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
