On 3/27/02 8:21 AM, "Claude Brisson" <[EMAIL PROTECTED]> wrote:
> 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 That shouldn't be true. > - and what if, after all, I want the global context to be changed sometimes ? Indeed. > 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. It's just a template language... :) > 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 ? > I posted a response to christoph, but I wrote a version yesterday in a J1 tech session that, shall we say, didn't hold my attention... I also found a little thing to change in the reference code, so you will need to get a snapshot from CVS for it to work.... -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting "Whoever would overthrow the liberty of a nation must begin by subduing the freeness of speech." - Benjamin Franklin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
