List<Integer> foos = new ArrayList<Integer>();
foos.add(5);
int foo = foos.get(0);
I completely agree on that one. This is way easier to read.
But try using a few static imports, some (String...) for parameters
in a method... (here's one quick read for static: http://
www.davidflanagan.com/blog/000028.html)
My point was merely, if the code move to 1.5 you need to enforce some
structure on the committers or the code can become tricky to trace
and debug.
Is a lot more readable, self-documenting, and type-safe as compared
to:
List foos = new ArrayList();
foos.add(new Integer(5));
int foo = ((Integer) foos.get(0)).intValue();
Entirely true.
Still, magnolia has been striving to use jdk1.4 methods only and I
think it's a good policy.
Most (if not all) of the methods used in magnolia do no require a
move to 1.5.
I would prefer to see a set of module that specifically requires a
JDK >= 1.5 (somewhere in the module definition), but keep the core in
1.4.
Nicolas,
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
