On Wed, Sep 22, 2010 at 7:38 AM, Kevin Wright <[email protected]>wrote:
> That's very much the point... If a file can't be found when you're first > trying to open it, then that's normal. > If a file can't be found after you've already been working with it, then > that's exceptional. > The semantic distinction that you're observing is correct, but distinguishing the two cases doesn't make practical sense. Whether the file is not present at opening time or disappears while you're using it, you will probably want to handle this error the same way, so throwing the same exception and catching it a little higher in the stack frame makes sense to me. -- Cédric -- 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.
