Date: Mon, 17 Feb 1997 09:24:30 -0500 (EST)
From: "..Nissim.." <nchudnof AT mbhs DOT edu>
To: "Ian 'DrDebug' Day" <Ian AT darkblak DOT demon DOT co DOT uk>
cc: opendos AT mail DOT tacoma DOT net
Subject: Re: [opendos] BAD Filesystems
In-Reply-To: <5t1LUIA1E6BzEwYq@darkblak.demon.co.uk>
Message-ID: <Pine.LNX.3.95.970217092339.15206B-100000@binx.mbhs.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Mon, 17 Feb 1997, Ian 'DrDebug' Day wrote:

> In article <Pine DOT GSO DOT 3 DOT 95 DOT 970216123325 DOT 28935D-100000 AT sparkie DOT gnofn DOT org>,
> "Colin W. Glenn" <cwg01 AT gnofn DOT org> writes
> >On Sun, 16 Feb 1997, Ian 'DrDebug' Day wrote:
> >
> >> I've been using 4DOS with DOS apps for years it allows command lines of
> >> upto 256 characters.  It simply only gives 126 to the application.  It's
> >> still useful to allow more (which are use for long filenames, internal
> >> commands etc.)
> >
> >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?
Not #include, @include. Like djgpp programs you can specify the command
line params in a file, and pass it as '[command] @[param_file]'.

...Nissim...
/%%%\___  -----------<MONTGOMERY BLAIR HIGH SCHOOL>------------  :::::
|o o|   _________________      _______________________________   |o o|
| ^ |  / E-mail:          \   / .....................WWW URL: \  | ( |
| - | < nchudnof AT mbhs DOT edu |   | http://mmm.mbhs.edu/~nchudnof  > | o |
`---'  \__________________/   \_______________________________/  `---'