[Boost-build] Variable expansion behaviour

From: Alex Besogonov (cyberax_at_[hidden])
Date: 2006-05-04 01:13:12

Good <time-of-day>!

I'm now porting variables expansion and I have some questions about it:

1. The original Jam doesn't work with paths containing braces, for 
example "temp/BuildPort)old/some" is a valid path on Windows. But
$(somevar:D="/temp/BuildPort)old/some") will give something like
"temp/BuildPort/$(somevar)old/some". Paths with colons don't work either.

I guess that this corner case doesn't cause a lot of problems for users. 
Do we need to have it fixed in my port (for the sake of perfection :) )?

2. Is there any test suit for variable expansion other than 
var_expand_unit_test method in the end of expand.c ?

3. Is it possible to add the build directory as an include directory to 
the list of usage requirements? The problem is that Bison generator 
produces .hpp file with parser definition in the build directory, so
other code can't include it.

-- 
With respect,
             Alex Besogonov (cyberax_at_[hidden])