On 11/17/2011 3:33 PM, Alexandru Ciobanu wrote:
On 2011-11-17, at 3:26 PM, Alexander Neundorf wrote:
Not sure how to achieve this.
A policy ?
Actually it is very easy to make it transparent and thus not need to modify any
.cmake files.
We just need to escape the curly brackets:
{ -> \{
} -> \}
in the regular expression before compiling it.
Well, as part of this we would like to offer the new matching capabilities
from using that syntax.
This would be an appropriate use of a policy. The OLD behavior would
escape { and } and the NEW behavior would not escape them (but of course
the user could escape them anyway). The old regex implementation could
be dropped completely. However, there may be contexts in which a regular
expression appears but we don't have a way to define the policy setting.
That will take some investigation.
-Brad
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers
