On Sat, 19 Jul 2014, Mateusz Viste wrote: > Hi all, > > I think this problem goes beyond "path separators". As I understand it, > any argument including a slash character will get exploded. So yes, this > might be used as path separator, but not only. For eg. sed expects slash > delimited values inside a single argument. > > @Juan - you also write about other "different issues and limitations" - > could you please post us a list? Even if FreeCom is semi-maintained > nowadays, it would still be interesting to know what kind of quirks you > found there..
command.com should not be splitting the strings at all, but should send the parameters "in the raw", terminated (iirc) by a newline. It is for the libc to parse them; if otherwise, that is a serious flaw. There *is* the option of 4DOS. -uso. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
