Hey stop bad mouthing macros :)
5's problems with macros is not that there are so many of them, but that documentation
and usage guidelines are hard to come by. The lesson, for Parrot developers to learn
from 5's macros, is that both macros and functions, the entire internal API, must
be documented. If new people are to ever learn and contribute, documentation on the
rational and perfered usage patterns is mandatory.
I think the improvements in the documentation of perl's internals in recent years
deserves a round of applause. Still, Parrot really must do better, if it is to
succeed.
Dave Goehrig
qw/ who is praying for parrot to support XS code,
cause he doesn't want to rewrite
SDL_perl's 11,000 lines /;
