Agree except +1 for having #directives in macros, you can cut and paste them
and without them, a library of macros would not be so useful.
Theo Keyzer
> Leon Messerschmidt wrote:
> >
> > Hi
> >
> > For what my vote is worth:
> >
> > +1 on including #macros ( disabled by default )
> > Although #macros can prove to be a powerful feature it should be used
with care
> > and therefore I think we should disable them by default to prevent
rookies of
> > shooting themselves in the foot. Kinda like stricter gun laws :-)
> >
> > -1 on allowing #macros or #directives inside #macros ( althought I don't
believe I
> > have a -1 voice )
> > As soon as you make calls to other #macros from inside a #macro you
create nested
> > structures that does not conform to the original idea for macros.
> >
> > The original idea (as far as I can see) is to provide template writers
with a
> > mechanism to ease template writing and avoid unnecessary copy/paste.
With calls
> > to #macros within #macros you can create sufficiently complex (and ugly)
code that
> > will come back to haunt you.
> I second Leon's vote (+1 on including them off by default, -1 on nesting
> macros). I'd like to reiterate that we need to be extremely careful
> with the management of Velocimacros.
> Daniel Rall
