On 25 Mar 2011 09:37, "Reinier Zwitserloot" <[email protected]> wrote: > > When we start arguing that a CPU/Memory only construct is "too slow", in regards to an I/O operation, you're grasping at some very tiny straws. >
Admittedly not the best example :) I'm just seeing this as part of a larger anti-pattern, where checked exceptions are used for non-exceptional return values and flow control, invoking the cost of building a stack trace in order to to so. I actually see this as an oxymoron, where the idea of a checked exception seems to be saying "here is a truly exceptional occurrence that you should expect on a regular basis" It isn't exceptional for some given string not to specify the valid path to a file. If anything, given a bunch of random strings, it seems more surprising that one *would* be valid. So FileNotFound should be a normal and very plausible return value, not something treated as exceptional. > > On Thursday, March 24, 2011 7:12:02 PM UTC+1, KWright wrote: >> >> Of course not, hence my desire to not waste time and resources building an in-memory representation of the thing! >> -- 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.
