Is the default behavior for Velocity to interpret a macro name that starts
with 'set' as the set directive instead of determining if it is a macro name
instead?
Example:
#macro( setPageAttributes )
...
#end
Using #setPageAttributes() results in a Velocity parse error (as follows).
Encountered "PageAttributes" at line ..., column ....
Was expecting one of:
"(" ...
<WHITESPACE> ...
Is this a bug or a known 'feature'? It seems that the VTL parser should be
smart enough to check for whitespace and/or parenthesis after a directive,
as #set'RestOfMacroName' should be distinguishable with #set( .... ) or #set
( ... ).
Thanks,
Jamie Stillman
CBC Companies
[EMAIL PROTECTED]
614.538.6076
There are only 10 kinds of people in the world:
those who understand binary and those who don't.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]