Mitch Capper wrote: > *With Path accidental separator detection* > The windows path branch tries to add either forward or backward path > separator support in windows. Clearly \ is also the escape char so it is > possible that there are places that A) windows paths that have escape chars > used will fail, as it is treated as a dir separator (and I don't have \\ > detection etc). B) there are places in code where '/' was being used as a > flag or not a path separator that I mistook for a path separator and now > '\' may have odd effects.
We certainly like to see fixes in this area. If I have understood it correctly, the best way to handle file names on native Windows is to - use '\\' as a directory separator when composing file names, - allow both '/' and '\\' when inspecting file names. Bruno
