From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-10 22:14:17
----- Original Message -----
From: "Matt Armstrong" <matt_at_[hidden]>
> It makes some sense for things like :P and :D -- the filename
> operations are OS dependent. Perhaps the win32 path functions are
> smart enough to recognize '/' as a path separator, but they use '\'
> when rebuilding the filename.
Of course I understand that. But who is this behavior helping? Surely any
system that depends on it is a fragile one. What's the scenario? To justify
the current behavior, it seems to me that all three of these conditions must
* The system supports user-specified paths with forward slashes
* The system happens to use these modifiers on all such paths
* The system depends somehow on the lack of forward-slashes in
paths that have been modified.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk