On Mon, Jun 13, 2016 at 16:14:51 +0200, Daniel Pfeifer wrote: > On Mon, Jun 13, 2016 at 2:09 PM, Ben Boeckel <ben.boec...@kitware.com> wrote: > > Usually NULL means "unset". See properties, > > variable values, etc. As an output, any place which doesn't care should > > already be using GetSafeDefinition(). > > I know that, at the moment, NULL is used for "unset" in many places. I > am trying to figure out whether we could theoretically use "empy" to > mean "unset". > If there is a case where we distinguish between null and empty, this > will not be possible.
And I'm saying that looking to port to GetSafeDefinition() will highlight those that *can't* be converted easily which will get you use cases for the current split. > > As a concrete example, `set(CACHE)` cares about NULL versus *s == NULL: > > Thanks for the example. I found the check for `s != NULL` in the > second line. Can you help me finding the check for `*s == NULL`? There isn't, hence the difference in behavior between NULL and empty. --Ben -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
