$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-02 12:02:20
Just tracking down bugs in our current code, I ran across this in
my -d+5 output:
os.path.is_rooted c:\tmp\rene\boost-build-test\Jamfile
Of course, that returns false, even on NT, because os.path expects to
operate entirely in terms of "normalized paths"... sometimes. The
interface specification isn't clear about which functions take native
paths and which take normalized paths. Why don't we just normalize all
paths internally if that's what it takes? Why burden the users of
os.path with keeping track of both normalized and non-normalized paths?
-Dave
+---------------------------------------------------------------+
David Abrahams
C++ Booster (http://www.boost.org) O__ ==
Pythonista (http://www.python.org) c/ /'_ ==
resume: http://users.rcn.com/abrahams/resume.html (*) \(*) ==
email: david.abrahams_at_[hidden]
+---------------------------------------------------------------+