Honza Pazdziora <[EMAIL PROTECTED]> wrote: > But 8.2 is not TRUE value. If returns_a_true_value is supposed to > return a true true value, it should end with > > return TRUE; > > shouldn't it?
Well, no. If it is supposed to return "a" true value, then it could return any true value, and 8.2 falls in that category. On a related, less non-serious note, I seem recall it was fairly standard in C, back in the old days, to write something like #define FALSE !1 #define TRUE !FALSE Since 1 is "a" true value, but TRUE is "the" true value. (And of course FALSE is "the" false value.) But that was in the days before standard C, which demanded that FALSE always be zero. Constants like this aren't (or shouldn't be) for testing, only for setting. -- John D. Porter __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus
