This order change still makes no sense to me. It confuses me even while
just reading the properties.
When I start reading a line from a property file, I immediately expect
finding what kind of property it is with the first token, just as it
happens in most property files.
If I find "resource", I immediately know that it is a resource related
property, but if I find "file", I have to go on reading the rest and
even looking up where the hell this "file" come from. And if the line
is something like
dbsource.resource.loader.modificationCheckInterval = 2
I will tend to think that it is some new data extraction thing instead
of a database resource loader, until I read the rest.
It is a fraction of a second but it is enough to slow down a visual
text scan.
Making a property file more English-like in word ordering and so makes
as less sense to me as trying to make English more Java-like.
Keep in mind that I am against the idea and not (at all) against the
person.
Thanks and have fun,
Paulo Gaspar
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Geir Magnusson Jr.
>
>
> ex (from the defaults)
>
> resource.loader = file
>
> file.resource.loader.description = Velocity File Resource Loader
> file.resource.loader.class =
> org.apache.velocity.runtime.resource.loader.FileResourceLoader
> file.resource.loader.path = .
> file.resource.loader.cache = false
> file.resource.loader.modificationCheckInterval = 2
>
