Neat: It's backward-compatible and makes macros more useful, so file it
under improvement and commit it. Two and a half Qs:
It looks to me like this implementation is safe against { and } in
strings, right?
(Not a new issue, but since we're on the subject of macros:) If I define a
macro named
I've committed it as of r11820. Since it parses by tokens, braces
inside of strings are allowed.
With regard to clashing, pir specials take precedent over macros. The
complications that could arise from accidental recursion, etc, seems
complex. As for your .local example, you can always
I finally got around to writing up a patch to parrot that would allow
the features I mentioned a while back. There aren't any heuristics,
just braces. The first file is a patch to imcc.l and imclexer.c(may as
well). The second file is a set of macro's I've already written up(not
documented
