On Wed, May 21, 2014 at 8:06 PM, Matthew Woehlke < mw_tr...@users.sourceforge.net> wrote:
> On 2014-05-15 08:36, Ben Boeckel wrote: > > On Thu, May 15, 2014 at 12:45:27 +0200, Nicolas Desprès wrote: > >> Nope. These variables are the cmake equivalent to the __LINE__ and > __FILE__ > >> C-pre-processor macro. What I need is the #line directive equivalent > which > >> force the value of these variables so that error messages reported by > cmake > >> uses the forced value. > > > > If you'd like to try a patch, the relevant code is in > > Source/cmExprParser*. Add a callback for #line nnn and update the > > CurrentLine variable cmExprParserHelper.cxx. Don't forget tests :) . > > > > This will also likely need a policy since there's no guarantee that > > #line "directives" don't exist in already existing code as comments. > > Maybe we should not introduce pragma-like constructs that are > indistinguishable from comments? :-) > > TBH I'd be a little ambivalent about such a feature. A line pragma > itself isn't too bad, but opening the door for other types of pragmas > makes me a little more nervous :-). > > If it is possible I would rather prefer a cmake macro too. -- 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
