Sorry if this has been covered in an old thread , but I'm confused...
Velocity needs a default constructor to pretend static methods aren't
static?
This is what I was referring to earlier - if we are going down the
reboot route, we should set some parameters to make sure a) our good
intentions don't bust anything silly and b) we don't spend months
tinkering instead of focussing upon what's important - shrinking the
Commons Collection JAR and stuffing generics into it.
---
Stephen Smith, MEng (Wales).
http://www.stephen-smith.co.uk/
Stephen Colebourne wrote:
For example. if we're really going to push the boat out on this, what
about hiding public constructors in static utility classes? It's the
sort of thing CheckStyle whines about, and normally with good reason.
I've never understood why CollectionUtils#CollectionUtils is public,
even with a comment along the lines of "should not normally be used".
If every method is static (and the class is therefore potentially
finalised), when would it ever be used?
Tools like Velocity need an instance as they can't handle static methods.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
