Closed tgockel closed 9 years ago
It won't be replaced with NULL
, but something like jsonv::null
. The issue with using nullptr
is that it represents "nullness" in C++ space, but not really in JSON space (where null
is a value of sorts). Imagine the error-proneness of jsonv::value*
.
Check out 652e0eee37f8991d28850f8bca73b6cc9a7b67a9 if that wasn't clear :-)
Got it! Good move. :-)
Why don't you want to use
nullptr
? Are you wanting backward compatibility? There are very good reasons to usenullptr
overNULL
which is usually a macro (shudder) meaning0L
.At the very least, you should use some other symbol that can be defined to be
nullptr
for those of us with a modern C++ compiler. :-)