Casper Bang wrote: > On 4 Aug., 20:22, v6ak <[email protected]> wrote: > >> Is it really a DISadvantage when you get compile error(s) because of >> incompatible API? >> > > Let me turn it around instead. Is it a good idea how InputStream.close > () throws a IOException? Can anything be done about it now? > In any case, the real problem here is the miss of a safeClose() method right in InputStream. With both variants, most people might use the simpler version, with the few people requiring a diagnostic to use the safer one. AGain, it's a library problem, rather than the language.
-- Fabrizio Giudici - Java Architect, Project Manager Tidalwave s.a.s. - "We make Java work. Everywhere." weblogs.java.net/blog/fabriziogiudici - www.tidalwave.it/blog [email protected] - mobile: +39 348.150.6941 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
