On 08/15/2013 09:09 AM, Brad King wrote:
> Fixed and test added:
>
> http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=9040ec91
Actually another side effect of the previous behavior that is
good to fix is in a case like this:
message(STATUS a # oops, forgot close paren
message(STATUS b)
With the missing paren the next line's "message(" looks like an
argument to the first message(... call and CMake warns that the
paren is not separated. With many lines after the missing paren
it causes a lot of warnings to appear before the actual error
message about the missing ")". That is distracting so it is
better to tolerate left parens not separated.
-Brad
--
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://www.cmake.org/mailman/listinfo/cmake
