You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Byron Foster (JIRA)" <de...@velocity.apache.org> on 2008/11/18 18:43:44 UTC
[jira] Commented: (VELOCITY-623) Modify escape behavior in strict
mode
[ https://issues.apache.org/jira/browse/VELOCITY-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648667#action_12648667 ]
Byron Foster commented on VELOCITY-623:
---------------------------------------
The parser needs to be changed for this, and most of the work involved I believe would be to maintain backward compatibility. I would rather make the change when backward compatibility is not an issue.
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org