Re: Re: Re: There's Only One Way To Do It

[exussum0]

In defense of deprecation, running java using a deprecated function will warn you. As for the java io stuff, it is rather unweildy. Unwieldy? It's a view of how things should be. Some people agree with it, some people don't. It's a problem with complex systems. People are more likely to agree on the simple end of life, not the more complex ones :\


-- "So far my experience has been that most people who go for certification have broad but not deep knowledge in the field and the flavor of the knowledge is academic. But every once in a while one finds a gem of a person who learns all the time and uses certification to prove it." -- on Orkut

[hardburn]

running java using a deprecated function will warn you.

I don't want it to warn me, I want the orginal fixed. One of the major selling points of OO is that you can encapsulate behavior, so DataInputStream.readLine should be fixed instead of moving that functionality somewhere else. You can deprecate methods if you decide the old design was broken, but if it's just the underlieing code that's broken, then you're ignoring one of the big benifits of OO by deprecating it.

[exussum0]

That's acceptable to a great agree. If it's broken, fix it. But what if the design is wrong. How can they replace the old design with a new design, while supporting the old one, and prevent new people from using the old design? Eventually, you have to break compatability.

They do this with java.io. They've ripped out some of the internals and replaced it with some of the nio stuff. But some stuff are just bad joojoo.. like Thread.stop().

-s


-- "So far my experience has been that most people who go for certification have broad but not deep knowledge in the field and the flavor of the knowledge is academic. But every once in a while one finds a gem of a person who learns all the time and uses certification to prove it." -- on Orkut