At Wednesday 2004-08-18 05:32, you wrote:
Jeremy Maitin-Shepard <jbms@attbi.com> writes:
I brought this up a while ago. I believe Beman stated as a rationale for this behavior that he and other boost developers and users like to use Windows native paths in Cygwin, using Cygwin as an environment for Windows software development.
I think that's a bad rationale. In point of fact most cygwin tools can handle either path format, but the native representation is indeed a POSIX one.
You can define BOOST_POSIX when compiling to force POSIX path handling. Arguably, POSIX should be the default on Cygwin, since it is designed to be a POSIX emulation environment, and many users surely use it as such.
Yeah. But IMO on cygwin boost::filesystem should handle both formats.
am I correctly inferring that it should check "both" filesystems for existence, etc.? should paths with '\' in them ONLY check the native windows filesystem while those with '/' the POSIX one? What if it has both? I see worms here, maybe only one or two, but perhaps and entire can.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"