The intent is to use a construct that works even with older CMake versions such that the code enclosed in the construct only gets run on the first configure.<br><br>I'm pretty sure it's only dangerous with variables that have dangerous names in the first place.
<br><br>Do you have a concrete example that is giving you problems?<br><br><div><span class="gmail_quote">On 11/13/07, <b class="gmail_sendername">Brandon Van Every</b> <<a href="mailto:bvanevery@gmail.com">bvanevery@gmail.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I see the same construct in CHECK_INCLUDE_FILES. What is the intent?<br>
This is not safe.<br><br>Cheers,<br>Brandon Van Every<br><br><br>On Nov 7, 2007 11:38 AM, Brandon Van Every <<a href="mailto:bvanevery@gmail.com">bvanevery@gmail.com</a>> wrote:<br>> It begins with:<br>><br>> MACRO(CHECK_C_SOURCE_COMPILES SOURCE VAR)
<br>> IF("${VAR}" MATCHES "^${VAR}$")<br>><br>> What is the intent here? If ${VAR} contains regex special characters<br>> you're going to get all kinds of weird and nasty behavior.<br>
><br>><br>> Cheers,<br>> Brandon Van Every<br>><br>_______________________________________________<br>CMake mailing list<br><a href="mailto:CMake@cmake.org">CMake@cmake.org</a><br><a href="http://www.cmake.org/mailman/listinfo/cmake">
http://www.cmake.org/mailman/listinfo/cmake</a><br></blockquote></div><br>