sebb wrote:
On 05/04/2009, Phil Steitz <phil.ste...@gmail.com> wrote:
sebb wrote:
The code already uses some 1.5 features, e.g. enum and autoboxing. It
also already uses parameterized types, just not everywhere. I think
it's too late for compile-time compatibility with 1.4.
That is not what I meant. I meant that I want the upgrade to involve the
least possible pain for users. That means, as much as possible, code using
1.x continues to work.
Agreed.
I think we were talking about different compilation processes.
I was referring to Math, and I (now) assume you were referring to code
that uses Math.
To give a concrete example, clone() and List<T>.get() etc no longer need casts.
Removing the cast prevents the code from being compiled under 1.4, but
does not affect other code compiled using 1.4.
OK, I have no problem with changes internal to [math] that do not force
changes in user code or change (unbroken) behavior.
Phil
Regarding raw types, the types are erased at run-time anyway. I think
the only affect on user code would be to generate some compile-time
warnings. I don't think it will stop code working. Anyway, the code
already uses non-raw types, it's just that some raw types have yet to
be converted.
Here again, what I want is to minimize user code breakage.
Agreed.
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
