You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Nathan Bubna (JIRA)" <de...@velocity.apache.org> on 2008/09/03 01:13:44 UTC
[jira] Resolved: (VELOCITY-395) Semantics of escaping unclear
[ https://issues.apache.org/jira/browse/VELOCITY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-395.
-----------------------------------
Resolution: Fixed
hopefully that commit helps...
> Semantics of escaping unclear
> -----------------------------
>
> Key: VELOCITY-395
> URL: https://issues.apache.org/jira/browse/VELOCITY-395
> Project: Velocity
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 1.3.1
> Environment: Operating System: Windows 2000
> Platform: PC
> Reporter: Frank Fischer
> Priority: Minor
> Fix For: 1.6
>
>
> I think the semantics of the escaping operator \ (backslash) are not documented
> clearly. Especially I miss this ones:
> Why generates
> \$foo ==> $foo
> but
> \${foo} ==> \${foo}
> this seems inconsistent to me. I expect
> \${foo} ==> ${foo}
> I understand that
> ${foo:bar}
> raises an error since there are no : (colons)
> allowed in a variable-name.
> But why raises
> \${foo:bar}
> also an error? I would expect that \$ disables the function of $
> as an operator, so that the following {..} will not be parsed as
> a variable name.
> There should be a simple way to generate something like
> ${foo:bar}
> or even
> ${not a variable name at all &%$}
> The workaround
> #set($D='$')
> ${D}{foo:bar}
> is undocumented and REALLY ugly.
--
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