Hi!
So, if my vote counts, I'd say that I am somewhat -0 on the concept in
general and I would see it as a non-core component (e.g. optional plug-in)
so people are able to try it out and if it shows not to be dangerous it can
be integrated into the core later. As for default bihavior I vote for
allowing macros & directives inside macros (BTW what are going to do about
recursion?). And also vote for only allowing macro definitions in a central
library and not in the templates themselves. dixi.
fedor.
> Hello,
>
> Can we please vote on the #macro directive today. If
> we want it in the core, and if so how it will
> behave by default.
>
> I think they are a powerful mechanism, but agree that
> they might possibly be the source of potential
> problems. This remains to be seen, and we probably
> won't be able to tell until some people try it.
>
> I'm am all for setting up default behaviour that
> is safe: that could range from turning off
> macros by default, to not allowing #macros inside
> #macros, to not allowing #direcitves inside macros.
>
> Insofar as the implementation, Geir has this
> worked out and he's ready to integrate his
> code. I will also help him if we agree that #macros
> are a good thing.
>
> So could everyone throw in their 2c today please.
>
> jvz.
>
> ---
>
> Jason van Zyl
> [EMAIL PROTECTED]
>
fedor.
_______________________________________________________
Say Bye to Slow Internet!
http://www.home.com/xinbox/signup.html
