Message-ID:	<19970217073254.31878@hagbard.demon.co.uk>
Date:	Mon, 17 Feb 1997 07:32:54 +0000
From:	Dave Pearson <davep AT hagbard DOT demon DOT co DOT uk>
To:	opendos AT mail DOT tacoma DOT net
Subject:	Re: [opendos] BAD Filesystems
References:	<Pine DOT GSO DOT 3 DOT 95 DOT 970216123325 DOT 28935D-100000 AT sparkie DOT gnofn DOT org> <5t1LUIA1E6BzEwYq AT darkblak DOT demon DOT co DOT uk>
Mime-Version:	1.0
Organization:	Hagbard's World
In-Reply-To:	<5t1LUIA1E6BzEwYq@darkblak.demon.co.uk>; from Ian 'DrDebug' Day on Feb 02, 1997 at 12:07:17AM +0000
Sender:	owner-opendos AT mail DOT tacoma DOT net

On Feb 02, 1997 at 12:07:17AM +0000, Ian 'DrDebug' Day wrote:

> >Well, programmers have been bouncing off that wall for years, which is why
> >many fine well written programs allow the use of @include files.
> 
> Did I miss something there?
> 
> What have #include files got to do with command line length?

He said @include, not #include. You know. You write the command line
to a rext file (perhaps a list of files to work on) and then invoke
your app/utility like:

	C:\>foobar @filelist

Then the programmer sees the '@' at the start of the option and reads
the command line from the file.

If you use DJGPP to compile your apps, the nice thing is that it does
the above for you, so, you find that argc/argv are populated for you
before main() gets called (and it will glob filenames for you as
well).  You can turn this off if you want.

-- 
Take a look in Hagbard's World: |     w3ng - The WWW Norton Guide reader.
http://www.acemake.com/hagbard  |  ng2html - The NG to HTML converter.
Also available in the UK:       |       eg - Norton Guide reader for OS/2.
http://www.hagbard.demon.co.uk  |   dgscan - DGROUP scanner for Clipper.

- Raw text -