Elysian Shadows

programmerinprogress wrote:Could you imagine the chaos if the C++ standardisation committee decided one day to start using different numbers for true and false? all hell would break loose!

Not true and false, just NULL. At the moment, it just happens to be that NULL is #defined to be 0 (== false). It's conceivable that at some point, on some C/++ library for some OS, NULL might be one past the system's max memory. I personally think that that's not a reasonable expectation, but it is conceivable. Hopefully you at least see the point =)

== NULL is "good practice" "in case they decide to change NULL from 0 to some other number"

Sounds like something XxStillAVirgin69xX would say...

Actually I heard it from someone that was more like ImaProfessional420, but I still don't agree with it.

If they decide to change the value of NULL, then we'll adapt. Until then, I will use if( [variable] ) and if(![variable] ).