Is it really a DISadvantage when you get compile error(s) because of incompatible API?
On 4 srp, 20:01, Casper Bang <casper.b...@gmail.com> wrote: > Exactly, which makes checked exceptions a versionability problem. When > is the last time you wrote something and got it right the first time? > > /Casper > > On 4 Aug., 19:42, v6ak <v...@volny.cz> wrote: > > > On 4 srp, 19:21, Casper Bang <casper.b...@gmail.com> wrote:> If you have a > > nice public API people are calling, how are you going to > > > maintain/extend this with a new checked exception type? The minute you > > > touch a method signature, you are breaking each and every existing > > > callee - and you can't simply overload the signature because > > > internally the JVM has no concept of checked exceptions. > > > The real problem is that the design is backwardly incompatible > > regardless there are or aren't checked exceptions. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
