Since you're soliciting opinions, i have to say that we should probably
just fully adopt Java's call-by-sharing semantics and not bother with a
configurable argument evaluation strategy for macros. I suspect that a
shift to call-by-sharing would not break the 90% of macros out there. I
don't have e
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
[
https://issues.apache.org/jira/browse/VELOCITY-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELOCITY-867.
-
Resolution: Fixed
Fix Version/s: (was: 1.7.x)
That seems the way to go. Commi
[
https://issues.apache.org/jira/browse/VELOCITY-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487102#comment-15487102
]
Sergiu Dumitriu commented on VELOCITY-867:
--
Or to the main project, the engine.
[
https://issues.apache.org/jira/browse/VELOCITY-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15486901#comment-15486901
]
Sebb commented on VELOCITY-867:
---
Can you not add a link on the main menu?
You could easil
