Because of the whitespace skipper, the spirit grammar used to only parse
up to the whitespace at the end of escaped markup, but a recent change
to spirit causes it to include the whitespace. Trim it in the action so
that it will work with both the old and new versions of spirit.
Apparently the test reporting system can't parse the test output as the
source was the executable. So change it to the source file.
Delete the Jamfile for the line-compare tool, as it doesn't do anything,
and could cause confusion. It would look like it could be used to change
the way that line-compare is built, but it can't.
Also changed to use a different directory for comparison, to avoid a name
clash. This is probably a good idea anyway.
Doesn't work that well, as there's an image too large for mobile devices, and a
lot of code with long lines. Will probably need some CSS work to get things
working.
Really not sure about this, but filesystem doesn't have great support
anyway[1], and this handles some unusual cases better.
[1]: https://svn.boost.org/trac10/ticket/5448
Before the idea was that check_glob would throw out any invalid globs, and then
if they somehow got through glob would just fail to match. I now feel it would
be better if it also complained on finding an invalid glob, although it will
only detect an invalid glob if the pattern matches up to that point.
Plan is to have a "release" that is the last version to compile with C++03.
Not a proper release as I'll try to add some more features before the
next Boost release.
It was incorrect because it was following symlinks. That means that a
build system wouldn't detect is a symlink changed. It's probably best
not to do any normalization at all and leave it to the build system.
