Re: [Boost-build] possible bug in c-scanner pattern matching

Subject: Re: [Boost-build] possible bug in c-scanner pattern matching
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2009-10-01 00:27:39

Fadi Beyrouti wrote:

> Hello,
> 
> I noticed that some implicit dependencies were not being found correctly in my
> C++ code. After some investigation I realized that the files that were not being
> found correctly are those that have a tab between the "#include" and the filename
> to be included. Looking at the c-scanner pattern rule (in builtin.jam):
> 
>        return "#[ \t]*include[ ]*(<(.*)>|\"(.*)\")" ;
> 
> It did make sense that no match was found. I tried to fix that the following way:
> 
>        return "#[ \t]*include[ \t]*(<(.*)>|\"(.*)\")" ;
> 
> But surprisingly it did not work. Now, I am not a regular expression expert so
> I am probably missing something.
> 
> Just thought of reporting the bug. If there are any suggestions for a fix, I
> would also really appreciate.

Can you try the above fix together with the nightly build of boost.build, as found
at http://boost.org/boost-build2 ?

Boost.Jam only recently gained support for escape characters.

- Volodya