possible bug in c-scanner pattern matching

View: New views
3 Messages — Rating Filter:   Alert me  

possible bug in c-scanner pattern matching

by Fadi Beyrouti :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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.

Thanks.

--
Fadi,


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Re: possible bug in c-scanner pattern matching

by Vladimir Prus-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Re: possible bug in c-scanner pattern matching

by Fadi Beyrouti :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Vladimir Prus <vladimir <at> codesourcery.com> writes:

>
> 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
>


Tried it. It still doesn't work.

--
Fadi,


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build