[
https://issues.apache.org/jira/browse/VELOCITY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660468#action_12660468
]
Byron Foster commented on VELOCITY-623:
---------------------------------------
I'm going to close this because it's related to the 2.0 issue of escape syntax,
which is better discussed in an issue that deals with the problem in general.
And yea, this should work for both macros and references.
> Modify escape behavior in strict mode
> -------------------------------------
>
> Key: VELOCITY-623
> URL: https://issues.apache.org/jira/browse/VELOCITY-623
> Project: Velocity
> Issue Type: New Feature
> Components: Engine
> Affects Versions: 1.6
> Reporter: Byron Foster
> Fix For: 1.7
>
> Attachments: StrictEscapeWithProperty.patch
>
>
> provides another property 'runtime.references.strict.escape' that when true
> modifies the behavior of escaping a reference when in strict mode, see
> discussion VELOCITY-618. The behavior is a as follows:
> $abc = <exception> - If $abc is not defined
> \$abc = $abc
> \\$abc = <exception> - If $abc is not defined
> \\\$abc = \$abc
> The backslash in front of a reference always prevents that reference from
> being evaluated, and the backslash is removed. This is true wether a
> reference is in the context or not.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
