On 11/6/05, Clinton Begin <[EMAIL PROTECTED]> wrote: > > No. But deprecation is a language feature that has become untrusted > anyway. I wouldn't let that stop me. > > I figure we'll depend on good old fashioned human communication, rather > than compiler warning messages. ;-)
Any type of warning would have worked as well. I'm just of the opinion that if we're following all the latest best practices for version x.1 of a product, it's reasonable to believe that our applications will continue to work with x.2, and so on, so long as we keep up with the advice communicated by the release notes. But, if there is some technical reason why it should be removed now, such as it doesn't work with JDK 1.4 and later, then that would seem like cause enough. -Ted.
