commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell" <flame...@gmail.com>
Subject Re: [lang] next version etc
Date Mon, 17 Apr 2006 04:48:41 GMT
On 4/16/06, Gary Gregory <ggregory@seagullsoftware.com> wrote:
> > -----Original Message-----
> > From: Stephen Colebourne [mailto:scolebourne@btopenworld.com]

> > >>35588: Part of the lang.text call.
> > >
> > > I need text.VariableFormatter. If 2.2 does not come out soon, I am
> going
> > > to pluck it out of there for our own use ;)
> >
> > Do you need all its complexity with escaping?
>
> I want to provide our users with highly flexible configuration files
> (and scripts) where Java system properties and environment variables are
> available.
>
> It is possible that some of our users would need escaping things like
> '$' and '{}'. The flexibility I would be willing to give up is what
> characters to use for $ and {}, but this is the part that adds the least
> amount of complexity.
>
> If you are thinking of removing the ability to do things that correspond
> to  "${aVarPiece${anotherPiece}}", then I am somewhat indifferent right
> now. It just seems like a lot of work to undo the code and the unit
> tests since the current implementation works and it well covered by unit
> tests. Furthermore, it seems to me like once a feature like
> VariableFormatter is released, implementing the above feature would be
> the next step in the evolution of the class. Just my POV though...

+1 to the escaping - it seems like it's just doing the right thing,
not an increased feature.

Increased feature would be:  ${ENV.foo}  :)   Where ENV means the
environment (or ${D.foo} where it means the standard env).

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message