[
https://issues.apache.org/jira/browse/VELOCITY-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562476#action_12562476
]
Stephen Colebourne commented on VELOCITY-406:
---------------------------------------------
I support this RFE for list access using [ ].
I expected the syntax ${someList[1]} to work in Velocity, and was surprised
when it didn't. Perhaps VELOCITY-533 has made this more feasible?
Personally, I only need the 'get' behaviour, and not the 'set' behaviour, but
they should be logically introduced together.
I also don't see the need for ${someList.1} to work - that seems like overkill
syntax.
> Improved Syntax for Maps and Collections
> ----------------------------------------
>
> Key: VELOCITY-406
> URL: https://issues.apache.org/jira/browse/VELOCITY-406
> Project: Velocity
> Issue Type: Improvement
> Components: Engine
> Reporter: Jörg Gottschling
> Priority: Minor
> Fix For: 1.6
>
>
> I would like to see some syntatic sugar for Maps and Collections and perhaps
> other Objects too.
> (I have read that there will be a syntax for map literals in 1.5, that's a
> first step.)
> I want to have something like in groovy:
> http://groovy.codehaus.org/Collections
> Scroll down to "Slicing with the subscript operator".
> PS: Please do never implement this terrible confusing groovy map bean syntax,
> where "map.foo" ist equivalent to "map.get("foo")".
--
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]
