On Thu, Feb 3, 2011 at 5:05 PM, Yonik Seeley <[email protected]> wrote: > On Thu, Feb 3, 2011 at 10:52 AM, Simon Willnauer > <[email protected]> wrote: >> I think we should even go one step further and make NaN an illegal >> value for maxScore. I think we should add an assert in the setter and >> the ctor. Objections? > > If we don't initialize w/ NaN, maxScore will never be set to NaN, right? > And if someone want's to explicitly call setMaxScore(NaN) for some > reason... might as well let them?
I think an assert will not hurt here. Just thinking of a user who does that unintentionally and we can find the issue quickly by telling them to run with -ea?! simon > > -Yonik > http://lucidimagination.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
