3 ms·
Breaking backwards compatibility isn't really an option, but if the compiler and IDE would discourage the use of legacy features that would be best. Just remov
by Pxtl 13y ago
Breaking backwards compatibility isn't really an option, but if the compiler and IDE would discourage the use of legacy features that would be best.
Just remove the legacy/ugly methods and packages from the autocomplete process, and warn with recommendations/flag as deprecated. You don't actually have to break anything.
- iSnow 13y agoActually, every IDE warns you if you try to use a deprecated method. They show as strikethrough in your source too. There are things like http://docs.oracle.com/javase/7/docs/api/deprecated-list.html#class http://docs.oracle.com/javase/7/docs/api/deprecated-list.htm... and IDE's know about this.
- bradleyjg 13y agoProblem is Sun^W Oracle hardly ever depreciates anything. There are 21 classes in that list (7 in java.*), out of a total of almost 4000 as of java 7.