On Tue, Jun 5, 2012 at 3:55 PM, Fabrizio Giudici <[email protected]> wrote: > It's easy to contrive that situation too, thinking of a consequentiality so > that the second error only happens in consequence of the previous one, or it > will happen only after you fix the previous one :-) > > But I'd say that both examples are inappropriate. The point is that I want > perhaps something that processes the batch up to the end, then I go to the > log file and see the NPE where they happened, versus the fact that I have a > result set which is apparently ok, but now I have to dig into it to 1) > search for errors and then 2) rebuild the sequence of things that happened > back to the error.
I wasn't meaning to argue that the one way is the only way. Rather trying to give my +1 to the argument of "use the correct tool." Ideally, a language should make either choice a fairly easy to spot and conscious choice by the programmer. (Well, in my ideal of the moment. :) ) -- You received this message because you are subscribed to the Google Groups "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.
