In my mind, the point of io2 (as in, the next version plus the possible repackaging) is to allow us to (re)write io2 with Java 5 in mind. For example, you would never use a raw type in the API or internally. Any other non collection generics APIs (array parameters) left would be for backward compatibility. But for new APIs, we just need to think what is the best for an API parameter, for example, an array or a generics collections? I think we are going with generics from now on.
Thank you, Gary > -----Original Message----- > From: Torsten Curdt [mailto:[EMAIL PROTECTED] > Sent: Monday, February 11, 2008 4:39 AM > To: Jakarta Commons Developers List > Subject: Re: [io] 2.0 Moving to minimum of JDK 1.5 > > >> Additionally, nobody stops us from shipping an io compat library > >> which translates the > >> calls original io 1.x calls for io2. That one can be used as real > >> replacement of old 1.x > >> series, but offers the possibility to use as much Java 5 specifics > >> as possible in the > >> new API (varargs, new interfaces, generics, enums, ...). > > > > I still don't see the need to overhaul the entire API. > > And I don't see the point why we shouldn't. Going from from java 1.4 - > > 1.5 usually means a bit overhaul. > No one forces anyone to switch from 1.x to 2.x. > > cheers > -- > Torsten > > --------------------------------------------------------------------- > 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]
