compiler plugin warning about unwanted silent pointer-to-bool conversions
C/C++ silently converts pointers to booleans, which is presumably seen as a good idea by lazy people, but it can occassionally silently break code in strange ways, most notably by selecting a bool overload when no matching overload for the pointer exists (OUStringBuffer::append() can break like that, e.g. in ba37e406, other cases are 8e3bf159 or 28e4c025). So far the plugin checks only conversions in function call arguments, there's disabled code that could check more places, but I'm not aware so far of any place where anything actually broke because of that, and it'd require fixups to be explicit in some places (e.g. 'bool b = returns_pointer();' would require '!= NULL' added), so for it'll be only the simple various and it can be made more strict if wanted. Change-Id: I6a5d207daf925e6c2d1bf684060536795ecfcc35
Showing
Please
register
or
sign in
to comment