> but then I realized that since it doesn't know about it, it doesn't actually > get the full line. It does only see the first 127 characters, > which is why you can get odd errors even though your line should be fine, > depending on where the break is...
Nice analysis :) The behaviour of silently truncating the command line may even be dangerous. Consider you are about to delete a file, and the file name changes because of the truncation... > > Makes me think that maybe we should write a FreeDOS Run-time Initialization > Routine for Open Watcom? They have the example wildargv.c. > I'll make a note, I'll see what I can do once I start porting DOG to OW :) > Thanks again for the explanation and the resulting deep dive! :P If you intend to work on it, perhaps it would be good to contact jmalak, the maintainer of the OpenWatcom v2 port, to add it directly to the OpenWatcom v2 LIBC startup code. https://github.com/open-watcom/open-watcom-v2 Currently the programs have to handle CMDLINE by themselves. At least I do not know any runtime that handles it by default. Bernd _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
