|
> I hate changing behavior from one release to the > next, but in this case I think it is a good change. I agree, David, that this is a good change. However, it would be nice if there were a concept of a "warning" message (as opposed to a hard exception). Sort of like the deprecation message used for methods. A method could generate a warning if an error was detected. The programmer would have a choice (probably via a global setting) of either accepting the default action or signaling an exception. There would also be an option for logging warning messages to a system logging device of some kind. Then, after one or two interim releases, the warning gets "promoted" to hard exception. This, of course, is Java internals stuff, and has nothing to do with the toolbox. On the other hand, I would suggest strongly that there be a specific document somewhere in each release that documents all potentially harmful changes (that is, a change that cause currently working code to no longer function). These would be in a "backwards incompatibility alert" document. Joe +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.