3 ms·
When is assigning a pointer to be boolean false intentional and correct?
by lurker19 15y ago
When is assigning a pointer to be boolean false intentional and correct?
- cpeterso 15y agoI think the -Wconversion-null warnings are the other way around: int i = NULL; Because of C++'s conflation of NULL and 0 (and now C++0x's nullptr).
- chandlerc 15y agoMost of the cases we ran into were metaprogramming techniques which test whether an expression is a valid null pointer constants. These got innocently applied to 'false' and trigger the warning needlessly.
- koenigdavidmj 15y agoDone that before...had a variable that was formerly an int: int foo = 0; But got changed into a non-integral type: Thing foo = 0; Turns out Thing had a copy constructor roughly like: Thing::Thing(Thing* old) : field(old->field) { } Needless to say, my program was not very happy.