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.. regards, Mateusz On July 19, 2014 12:09:51 AM GMT+02:00, Juan Manuel Guerrero <juan.guerr...@gmx.de> wrote: >Am 18.07.2014 22:30, schrieb Rugxulo: >> Hi, >> >> On Fri, Jul 18, 2014 at 2:00 PM, Juan Manuel Guerrero >> <juan.guerr...@gmx.de> wrote: >>> I do not know if this is the right place to report this FreCom issue >> Dunno, not sure it's actively maintained by anyone anymore. >I feared this. > >>> I do not know if this issue is already well known but I would like >to >>> report it anyway. >>> >>> If I use FreeCom 0.84-pre2 XMS_Swap [August 28 2006 00:32:15] >shipped >>> with FreeDOS 1.1 and start the batch file in exactly the same way I >get >>> the following output: >>> >>> As can be seen, FreCom seems to interpret any slash as an option >marker >>> like in "/?" to get help. All microsoft command.com versions and >also cmd.exe >>> do interpret the slash as an option marker only if it is preceded by >some >>> kind of blank character. This makes it necessary to quote paths >written in >>> unix-style like: >>> "../foo/bar/." >>> if they shall be passed as arguments to a batch file to be processed >by FreCom. >>> Is this behavior a bug or a feature? >> I definitely reported this same quirk to somebody a few years ago. >> Obviously it was never fixed. It was probably just an unintentional >> flaw or too obscure to worry about. I mean, most DOS programs don't >> use *nix slashes as path separators. >> >> I wish I had better news for you like, "I made a fix", but it's not >> really that easy. (Not impossible, just very annoying.) >> > >This is not really disappointing. I was only testing for the >possibility >to recommend the FreeDOS 1.1 distribution as an alternative to >WinXP and/or Win98SE to build DJGPP ports but this seems not >really be possible due to different issues and limitations. ------------------------------------------------------------------------------ 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
