|
Boost : |
From: Glenn Schrader (gschrad_at_[hidden])
Date: 2007-01-08 14:05:54
Rene Rivera wrote:
>
> This would not be the way I would fix it. It will have the likely effect
> of breaking a bunch of other stuff that uses the regex function in bjam.
> The easier fix is to change the regex itself to include the newline as:
>
> local command-info = [ MATCH "^[^ ]+[ ]+[^ ]+[ ]+([^
> ]+)[^(]*[(]?([^)]*)"
>
> Yes that's a literal newline at the end of the first line. If you could
> test with that change the would be wonderful :-)
>
>
Yep, that works. Even so, that invisible trailing space character strikes
me as an editing mistake waiting to happen. Would it be worthwhile to
add explicit syntax to the parser for handling these cases so that they're
at least visible?
-glenn
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk