On Sunday, March 27, 2011 5:33:52 PM UTC+2, KWright wrote: > > > I think there's a middle ground here... Make all exceptions unchecked, > until such time as they're declared in a throws clause. >
This doesn't seem like a good idea. Let's say I take that snippet again - reading a resource file in my own jar. How does this work? this method explicitly throws an IOException, so your plan is that I must handle it. But in this case I dont want to. So what do I do so that I don't have to rethrow it? > "ignores" is a nice idea, but an absolute non-starter, you have a > snowball's chance in hell of getting another keyword added to the language > > Wow, already painting the bikeshed? Cripes. There are a bajillion ways to avoid a keyword here, but you don't even have to jump through any hoops for that. This is one of these cases where adding a context-sensitive keyword is 100% backwards compatible and is not going to have a measurable negative impact on the parser's ability to generate appropriate error messages - because where an 'ignores' clause can appear is extremely limited and can occur only after the parser already knows this must be the signature part of a method declaration node. > > -- 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.
