On Sat, June 6, 2015 13:36, Stephen Kelly wrote: > Code for Policies is also often complex. I often encounter Policies which > are ancient and which get in the way of code clean up generally.
Exactly the reason I don't understand why you'd want to add another policy to affect policies. Won't this complicate things even further? If you want so much to remove some ancient code, just do that instead. After all, you want this new policy to recommend using older cmake release anyway, so what's the difference (except that removing old policy will not _recommend_, but _force_ someone to use older release, which is normal practice in most/all the other programs I'm using)? As a side note, removing the policies will result in CMPXXXX (where XXXX > 1) to become the first policy, which one may find odd. You might also think of starting to give policies symbolic names instead of sequential numbers. Regards, Mike -- 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
