velocity-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Bubna (JIRA)" <>
Subject [jira] Created: (VELOCITY-692) have #if handle empty strings/arrays/collections/maps more conveniently
Date Tue, 10 Feb 2009 20:37:59 GMT
have #if handle empty strings/arrays/collections/maps more conveniently

                 Key: VELOCITY-692
             Project: Velocity
          Issue Type: New Feature
          Components: Engine
            Reporter: Nathan Bubna
            Priority: Trivial

An idea from the dev list:
On Sat, Feb 7, 2009 at 3:41 PM,  <> wrote:
> Hello,
> I wanted to share with you a few ideas I have about new simple
> improvements for DisplayTools. I should be able to make patches for
> them if you are interested.
> 1. Add new method
> isEmpty(object)
> that will return true if the object is null or empty (for strings it's
> zero length; for collections, maps and arrays it's zero size). This
> should help with  annoying null checks. (Probably a better place for
> this method would be Engine, not Tools)

yeah, not something for tools.  would be interesting to have the
Uberspect pretend that every non-null reference has an isEmpty()
method, or perhaps just add 0-length strings, empty collections, empty
maps and 0-length arrays to the list of things that #if( $foo )
considers false.

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:
For additional commands, e-mail:

View raw message