Hi Brad, unfortunately I failed to file an issue to keep track of this feature request. Gitlab always recognizes the text as spam and discards it.
I tried the following title and text: ```````````````````````````````````````````````````````````` Title ----- Function and macro definitions should obey the same scoping rules as variables Text ---- Hi all, as Brad confirmed on the [mailing list](https://www.mail-archive.com/cmake@cmake.org/msg55886.html), functions and macros are currently scoped globally. This means that any function definition in a sub scope (e.g., created via `add_subdirectory`) can redefine functions for the parent. The fact that CMake also always picks the last definition it encounters additionally introduces the problem that the order in which CMakeLists are processed can change the behaviour of the build system. This feature request therefore propose that function and macro definitions should obey the same scoping rules as variables to mitigate this potential pitfall. ```````````````````````````````````````````````````````````` Do you have any recommendations on how I can resolve this? Cheers, Mario -- 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
