On Wed, Sep 22, 2010 at 3:27 PM, Ricky Clarkson <[email protected]>wrote:
> Without exceptions how else is the file system supposed to communicate all >> the different causes of failure? Basically what your describing is what we >> have today with File.delete and friends where it's a pain to figure out why >> a delete rename and similar actions fail. Half the time all yiu want is >> message that a human can read etc. By not throwing an exception you've just >> made my code larger all so I can call an api to get a message. Every other >> solution except for an exception is more verbose and requires state and s >> definitely less functional. In goes the filename, give me a file or >> complain. How can that possibly be made simpler ? >> >> > File.delete returns a boolean. Surely you can think of something more > descriptive it could return. > And yet others have been arguing how testing against null is better than catching an excecption. -- 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.
