[
https://issues.apache.org/jira/browse/VELOCITY-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567840#action_12567840
]
Nathan Bubna commented on VELOCITY-587:
---------------------------------------
If you ask me, the only thing in double-quoted strings that should behave
differently than it does in a template in general is the double quote (which
ends that string and therefor cannot currently be directly put in double-quoted
string). A backslash in a double string should follow the same rules as a
backslash in a template in general (i.e. only meaningful for escaping valid
references/directives/macros). It definitely shouldn't be a parsing error and
ideally should not warrant a section in the user's guide.
> Backslashes throw lexical errors in double-quoted strings
> ---------------------------------------------------------
>
> Key: VELOCITY-587
> URL: https://issues.apache.org/jira/browse/VELOCITY-587
> Project: Velocity
> Issue Type: Bug
> Affects Versions: 1.6
> Reporter: Jon Seymour
> Priority: Minor
> Fix For: 1.6
>
>
> The VTL doesn't currently provide a way to express strings containing a
> single backslash (\)
> #set($backslash="\")
> results in a lexical error during template parsing.
> #set($backslash="\\")
> results in $backslash being assigned a string containing two backslashes (\\)
> It appears the only workaround available now is to construct a variable
> containing just a single backslash with this idiom:
> #set($twobackslashes="\\")
> #set($backslash=$twobackslashes.substring(0,1))
> Even if this can't be fixed in the parser, the documentation should be
> updated to define a preferred idiom for obtaining a string containing a
> single backslash.
> jon.
> note: this issue partially duplicates a comment by Guido Deinhammer on issue
> #454 regarding other escaping issues. I have raised a separate issue, so that
> this one can be addressed separately, if desired.
--
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]
