We all know that testing can't cover everything even under ideal circumstances, and even if it did and you caught this in testing it would be better to have a stack trace than an empty string. Wouldn't you agree,? On Jun 4, 2012 2:51 PM, "Fabrizio Giudici" <[email protected]> wrote:
> On Mon, 04 Jun 2012 16:43:20 +0200, Ricky Clarkson < > [email protected]> wrote: > > I disagree on the defaults issue. It's better to have an error of some >> kind that points you directly at the source of a problem than simply a >> missing word or a nonsensical one. >> >> Dear unknown, >> >> Your bank account null has a $NaN balance. >> >> Thank you, >> $DEPT >> > > +1: all boils down to proper testing and get the output you expect. > > -- > Fabrizio Giudici - Java Architect, Project Manager > Tidalwave s.a.s. - "We make Java work. Everywhere." > [email protected] > http://tidalwave.it - http://fabriziogiudici.it > > -- > 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 javaposse+unsubscribe@** > googlegroups.com <javaposse%[email protected]>. > For more options, visit this group at http://groups.google.com/** > group/javaposse?hl=en <http://groups.google.com/group/javaposse?hl=en>. > > -- 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.
