Message-ID:	<5t1LUIA1E6BzEwYq@darkblak.demon.co.uk>
Date:	Mon, 17 Feb 1997 00:07:17 +0000
To:	opendos AT mail DOT tacoma DOT net
From:	"Ian 'DrDebug' Day" <Ian AT darkblak DOT demon DOT co DOT uk>
Subject:	Re: [opendos] BAD Filesystems
In-Reply-To:	<Pine.GSO.3.95.970216123325.28935D-100000@sparkie.gnofn.org>
MIME-Version:	1.0
Sender:	owner-opendos AT mail DOT tacoma DOT net

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?

-- 
DrDebug

---------------------------------------------------------------------
Ian 'DrDebug' Day         | Email:           Ian AT darkblak DOT demon DOT co DOT uk
Dark Black Software Ltd.  | WWW:      http://www.darkblak.demon.co.uk
The Home of MrDebug       | Dark Knight BBS & Fax: +44 (0)1480 471465
(THE Clipper debugger)    | Tel:                   +44 (0)1480 403104
---------------------------------------------------------------------

- Raw text -