It may be the last big subject to address before releasing 2.0: how to
handle macro arguments?
Those three issues exhibit nasty side effects of the current behavior:
https://issues.apache.org/jira/browse/VELOCITY-683
https://issues.apache.org/jira/browse/VELOCITY-684
https://issues.apache.org/jira/browse/VELOCITY-752
There also is a great wiki page on the subject:
https://wiki.apache.org/velocity/MacroEvaluationStrategy
As for space gobbling, the correct behavior is probably to have a
configuration parameter (something like
'velocimacro.evolution.strategy', which would take values like 'macro',
'relaxed' for the current behavior, and 'sharing'). Also, we ought to
avoid making a difference between string literals and other literals.
But I'd appreciate to hear your thoughts on the subject. Especially:
- how should the local scope, if present, affect the sharing mode?
- how should the macro mode behave if one tries to assign a value to
an lvalue?
Claude
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
