Brad King wrote: > cmState: Expose list of properties of values in the cache > https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=63c0e92c
The way these classes are designed, cmState is intended to be the way to access state which generally does not change during a CMake configure run in a way which would be observable to and relevant to the daemon. Things which do change in such a way should be accessed through cmState::Snapshot, or classes which depend on cmState::Snapshot such as cmState::Directory for directory properties, or some day cmState::Target for target properties. That way those properties can be versioned. It is true that some existing things in cmState should not be there (commands, cache properties etc). You can consider whether now is the time to move the cache property access to cmState::Snapshot (even without versioning internally) instead of adding more methods related to cache properties to cmState directly. Thanks, Steve. -- 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
