[ 
https://issues.apache.org/jira/browse/VELOCITY-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994810#comment-16994810
 ] 

Thomas Mortagne commented on VELOCITY-904:
------------------------------------------

Actually I found another issue related to this retro compatibility option:

{code}
{{velocity}}
#macro(macro1 $return)
1: $return
#macro2($param2)
1: $return
#end

#macro(macro2 $return)
2: $return
#end

#macro1($param)
{{/velocity}}
{code}

1.7:
{noformat}
1: $param
2: $param2
1: $param
{noformat}

2.2-SNAPSHOT:
{noformat}
1: $param
2: $param2
1: $return
{noformat}

The sub macro call "break" the parameter.

> Add a flag for better backward compatibility with null macro arguments
> ----------------------------------------------------------------------
>
>                 Key: VELOCITY-904
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-904
>             Project: Velocity
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: 2.0
>            Reporter: Claude Brisson
>            Assignee: Claude Brisson
>            Priority: Minor
>             Fix For: 2.2
>
>
> See [this 
> comment|https://issues.apache.org/jira/browse/VELOCITY-542?focusedCommentId=16621819&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16621819]
>  :
> {code}
> #macro(testmacro $parameter)
>   $parameter
> #end
> #testmacro($return)
> {code}
> bq. which used to print "$return" (when $return is null or undefined) and we 
> now get "$parameter". 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org

Reply via email to