DO NOT REPLY [Bug 34989] New: - "Formal" directive notation

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

DO NOT REPLY [Bug 34989] New: - "Formal" directive notation

Bugzilla from bugzilla@apache.org
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG?
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34989>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND?
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34989

           Summary: "Formal" directive notation
           Product: Velocity
           Version: 1.5
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Documentation
        AssignedTo: [hidden email]
        ReportedBy: [hidden email]


Unless it's something I have to enable (and I've seen no mention of that in any
documentation), I don't believe using curly brackets to surround directives
actually works.  According to
http://jakarta.apache.org/velocity/user-guide.html#Directives "Like references,
the name of the directive may be bracketed by a { and a } symbol."  I tried the
example in that section:

## First, a bit I added:
#set( $a = 1 )
## The actual example line:
#if($a==1)true enough#{else}no way!#end

The output of this is, unexpectedly:

true enough#{else}no way!

And if $a is set to 2 (for example), there is no output at all because the
#{else} is not spotted.

--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]