[ http://issues.apache.org/jira/browse/VELOCITY-430?page=comments#action_12363127 ]
Daniel Rall commented on VELOCITY-430: -------------------------------------- It seems like a needless complication to the parser to muck with a long-standing behavior (albeit in a backwards compatible manner). Additionally, this change reduces the syntactic difference between Velocimacro and Java object invocation (leaving the $/#, and possibily formal reference notation differences); this part could be construed as an usability improvement. > Allow commas or spaces to separate macro arguments > -------------------------------------------------- > > Key: VELOCITY-430 > URL: http://issues.apache.org/jira/browse/VELOCITY-430 > Project: Velocity > Type: Improvement > Components: Source > Reporter: Will Glass-Husain > Assignee: Will Glass-Husain > Priority: Minor > Fix For: 1.5 > > If there is a macro "displayNotes", it'd be nice to allow > #displayNotes("note1" "note2") OR > #displayNotes("note1" ,"note2") > Allowing macros to support comma separated arguments like almost every > programming language in existence. This never made sense to me. > Anyone object to adding this? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
