In E6 Damien writes about macros:

"As soon as it has parsed that subroutine call (including its argument
list) it will detect that the subroutine &request is actually a macro, so
it will immidiately call &request with the specified arguments".

If macroness is found *after* parsing the arguments, when does the "is
parsed" trait's action kick in?

Elsewhere, he writes:
"The 'is parsed' trait tells the parser what to look for  immediately
after it encounters a macro's name".

I would guess that the latter is what is intended. Or is it that the
absence of an explicit "is parsed" changes the behaviour (for efficiency
reasons, perhaps, as many common uses will parse arguments in standard
ways [though act in mind warping ways] ) ?

abhi.

Abhijit A. Mahabal                        http://cs.indiana.edu/~amahabal/

Reply via email to