On 4. September 2014 16:38:21 MESZ, Ruslan Baratov via CMake <[email protected]> wrote: >On 04-Sep-14 18:09, Anders Lindgren wrote: >> make sure that the argument don't form a valid variable name. >It's not possible > >> >> set(a b) >> set(b c) >> if(">${a}<" STREQUAL ">b<" OR ">${a}<" STREQUAL ">c<") >> message("true") >> endif() >How about that: > >set(a "") # variable `a` is empty >set("><" ">b<") > >if(">${a}<" STREQUAL ">b<") > message("Value of variable with name `a` is `b`!") >endif()
I really do not understand this argument. Do you have so little control over your build tool (and that's what CMake is)? Nobody makes variables like this. Maybe to break the build script on purpose. And then, it breaks, so what? HS -- 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
