Closed teotigraphix closed 5 years ago
That's an interesting observation, in previous NDK versions nullptr wasn't part of the STL of choice nor language level (which is hardly an excuse as it was a #define away). To me, the biggest problem is that it is confusing to determine whether the code refers to an actual numerical 0 instead of "unallocated memory space" (even though they imply the same on a technical level, it doesn't help code understanding).
Yes, it was due to the fact your code reads so well and the 0 for nullptr was like not having a period or comma.
Nothing earth shattering but, you know. :)
Is this legacy in the code that you use
0
asnullptr
?I am coding convention OCD sometimes and I have read not using
nullptr
is bad form.Here again, I am just getting into the deeper nuances of C++ now and I want to do things correct.