Moritz Lennert wrote: > > some things are specified Win style, > > some Unix style ... > > AFAIU, Windows understands both \ and / as path separator, so it > shouldn't make a difference, but you are right that we should unify this > if we can to avoid confusion.
The shell (cmd.exe or command.com) only accepts \. A / is treated as marking a flag, even when it occurs in the middle of a word. Given that GRASS uses / internally, there may be problems with passing Windows filenames to modules. If the filename is passed directly to e.g. fopen(), there won't be a problem, but attempting to parse the filename with e.g. strchr(..., '/') will cause problems. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list grass-dev@grass.itc.it http://grass.itc.it/mailman/listinfo/grass-dev
