On Sun, Jun 23, 2002 at 09:50:02PM +0100, Tim Bunce wrote:
> Much more likely is some kind of wrapper that manages a simple
> perl5-like run-time environment (stacks, marks, gimme, symboltable
> etc) plus source-code compatibility support (macros, functions etc)
> that's just sufficient to keep ol
Melvin's quip regarding macros, while harmless in itself, is, I fear, a symptom
of a real problem. One of the muses for parrot and perl 6 has always been
the inaccessibilty of the perl 5 code base. Perl 5's reliance upon
macros has been cited often as a source of confusion, by those attempting
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 doc
