Jason van Zyl wrote:
> 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.
+1 to macros in general, I think that they should
go into the core package too.
We should provide an option do disable macros if desired.
I think that we should allow nested macro expansion
including recursion (direct and indirect). Recursive
macros can be a great tool for rendering tree structures
if only stop conditions are correct.
As a security measure against infinite expansions, we
could have an option to set maximum depth of expansion
nesting. This could be used to disable nesting at all
(0), set to some small value to allow composite
macros, or set it to a large but finite value to allow
rendering of complex trees.
Macros that define another macros in their body should
not be allowed in my opinion.
We should also set a policy regarding redefinition
of macros. (Ignore, Exception, Overwrite). The policy
could differ on user / builtin macros.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
