Wouldn't trimming the spaces in the reading of the properties be the wrong place for this? Shouldn't the code using the property decide if it wants to trim or not?

I do agree that depending upon whitespace transferred through properties files sounds like one would be asking for trouble, having the reading code dictate the no-space policy seems worse.

geir

On Friday, March 7, 2003, at 01:39 PM, Thilo Schwidurski wrote:


"Tim Colson" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED]
Thilo - this begs one more question...

Do we really want to trim properties at all?? I think not.

You are kidding. Are you? You must. You definitely don't want to deal with
the resulting problem of this two "differing" properties.


resource.loader = file
resource.loader = file

(well, ok, you are warned now and will always watch out, I guess;-)

(and ok, OE *is* trimming the trailing space of the second property line -
d'oh)


I want five spaces if I type this:
"aproperty=     FIVE_SPACES_BEFORE_AND_AFTER   "

This won't work because the leading spaces are trimmed anyway.


And if I don't want them, I'd type this:
"aproperty=NO_SPACES_BEFORE_AND_AFTER"

Otherwise, somebody will write in soon saying "Why are Velocity
Properties chomping my space chars at the end of a line?????" :-)

Ok, you are kidding... ,-)


Bye,
Thilo.







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Geir Magnusson Jr                                   203-956-2604(w)
Adeptra, Inc.                                       203-434-2093(m)
[EMAIL PROTECTED]                                   203-247-1713(m)


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to