[
https://issues.apache.org/jira/browse/VELOCITY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638467#action_12638467
]
Nathan Bubna commented on VELOCITY-623:
---------------------------------------
Is there any particular reason the escaping has to be related to strict mode?
This is an improvement, as it shows the user intended to change escaping
behavior. But, could this change in escaping behavior work even without strict
mode on? Also, what about escaping directives and macros?
> 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
> 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]
