🚀 go-pugleaf

I've patched the setargv.asm that comes with BC++ 3.0 to be "4DOS-aware".
What it effectively means is that the extended (256 char) command line
length of 4DOS is recognised by the program. This adds about 100 bytes
to your program, and of course leaves it 100% "non-4DOS" compatible...
 
What it doesn't (yet) do, is supply 4DOS-like wildcards expanded on the
command line. I reckon that because of the TAB/F8/F9/F10 functions in
4DOS there is no big need for this. (Oh, BTW, 4DOS-people, there wouldn't
happen to be some undocumented 4DOS replacement for DOS's find-first,
find-next directory browsing calls?? That'd really help, I guess.)

OK, now comes the tough part ;)... I've studied Borland's license agreement
on the source code, and I think that it means that:
 - the modified setargv.asm file is still (C)opyright Borland, Inc., and I
   cannot distribute it as source.
 - I still can do whatever I want with my own code, so I will be able to
   distribute this thing as a patchfile to be applied to your own copy
   of setargv.asm
 - Distributing compiled binaries isn't forbidden, so I guess I can also
   send people the various .OBJ files for different memory models to
   include in their libs.

Was I correct on this? I sure hope so... (Sidney? Still out there? ;)

If you are interested in this, I can send you this, in either or both of
the following ways:
 - a "diff -c" file that can be applied to setargv.asm via "patch"
 - a bundle of .OBJs for various memory models.
 
I doubt whether this is general enough to warrant an upload to the major
ftp sites, but if the interest is big enough, who knows...

Regards,
-- Jan-Pieter
cornet@duteca.et.tudelft.nl