bbv2 current-disk relative paths

From: Johan Nilsson (johan.nilsson_at_[hidden])
Date: 2004-10-26 04:28:10

Hi,

how should "current-disk" relative native paths be handled, e.g.:
"\foo\bar\giz.h" (windows), "[foo.bar]giz.h" (vms)? Are they accepted at all
(I couldn't find any tests for those for the windows platform)? I'm not sure
on how one should to represent these in the portable path notation.

Also, I have some "echo" statements that I'd (might) like to keep (but
normally the should run silent) in the path conversion methods. Is there any
supported way of doing this so that they are only output when only running
the build system tests, i.e. some trace level when testing the build system?

And, what about using assertions inside the build system code (excluding the
test code), is it considered ok or does it slow down stuff too much?

// Johan