Adam Cameron said the following on 08/15/2010 05:12 AM: > On OpenBD the file path is using the wrong separator: a fwd slash > instead of a backslash (I'm on Windows here... obviously / would be > fine on *nix). This means if one pastes the "path" into a file-open > dialogue, the Windows Explorer Shell just goes "huh? Wazzat?". > Have you tried it? I have it on good authority that fwd slashes do work because we used then all the time when we used to we Windows:
http://bytes.com/topic/python/answers/23123-when-did-windows-start-accepting-forward-slash-path-separator#post85372 The only place where Windows balks at fwd slash in at the command line not enclosed in a quote because "/" is a switch delimiter. And if you want the well-know Corfield rant: http://corfield.org/blog/post.cfm/Backslash_is_NOT_a_path_separator Glad you figured it was MXUnit. .pjf -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon official manual: http://www.openbluedragon.org/manual/ Ready2Run CFML http://www.openbluedragon.org/openbdjam/ mailing list - http://groups.google.com/group/openbd?hl=en
