In what context? When opening a named file, it should be normal control flow to discover the name isn't valid. When performing subsequent operations on an already-opened handle, it's truly exceptional if the thing has since gone missing,
combining the operations is just poor design 2010/9/21 Cédric Beust ♔ <[email protected]> > > > On Tue, Sep 21, 2010 at 3:47 PM, Kevin Wright <[email protected]>wrote: > >> What would you propose as a good example? >> > > An example of a good checked exception? > > How about FileNotFoundException? > > -- > 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]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- Kevin Wright mail / gtalk / msn : [email protected] pulse / skype: kev.lee.wright twitter: @thecoda -- 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.
