On Thu, May 22, 2014 at 3:16 PM, Brad King <brad.k...@kitware.com> wrote: > > One remaining challenge is CMAKE_CURRENT_LIST_FILE and > CMAKE_CURRENT_LIST_LINE. Since the "current file" is not > handled by the lexer these may not be consistent unless some > kind of refactoring is done in the language implementation. > However, it is not clear whether CMAKE_CURRENT_LIST_FILE can > safely refer back to some transformed location because sometimes > code uses it to look next to the file being processed to locate > other files. If some source location mapping is in place then > that may not be well-defined. >
I think we should not touch those variables because they have dynamic behavior and if they are used in the generated code I expect the current behavior. Why not adding __FILE__ and __LINE__ tokens that would be expanded by the lexer with the file name and line number last set by #cmake-source-line? -- Nicolas Desprès
-- 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/cgi-bin/mailman/listinfo/cmake-developers
