On 3/27/02 8:42 AM, "Christoph Reck" <[EMAIL PROTECTED]> wrote:
> Claude Brisson wrote: >> >> Thank you for your responses, Christopher & Geir. >> [snip] >> 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 > > If you looked the ForeachDirective source and understood how parameters > are passed to directives, then you can go ahead and implement it. > > Geir, would a LocalDirective make it into the core or into the contribution > sections? > I did one yesterday in a boring session here at J1, and just put it into whiteboard/geir Give it a look. I really don't think we should jump ahead and make this core - we can support it in a contrib section, and if people really, really find it useful, we should talk about adding it, but I don't think it's really a core function... Just my 0.02 > I you do not get flamed on cons about implementing a local directive, and > Geir states he can put it into CVS, then you can read it as a "go ahead". With pluggable directives, anyone can implement anything. If there are good contribs, we keep them. But we don't have to add them to the core if they are not obvious or in widespread use. Having 'local variables' is something that makes a lot of sense to us programmers, but I would bet means very little to designers. I personally have a use for this, but I don't think many people do. Geir -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting POC lives! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
