10 Reasons We Need Java 3.0
Subject:   Obsolete code **can** be phased out
Date:   2002-08-06 05:32:22
From:   davecb
I had though I'd posted this in full before, but
I don't see it...

To oversimplify, with each new dot-release of
the product
x.1) declare bad idea denigrated
x.2) start generating warnings about the bad idea
x.3) generate error, but provide a do-not-fail
option so that old .class file can
stil be linked (fir folks who don't
have the source to something they bought)

In three releases, we could have a bad feature
complete obsoleted, without causing people who
have just libraries to lose their investment.