To: opendos AT mail DOT tacoma DOT net
Subject: Re: [opendos] OpenDOS + Win95 w/FAT32? 
Message-ID: <19970203.183342.4575.4.chambersb@juno.com>
References: <Pine DOT GSO DOT 3 DOT 95 DOT 970202233936 DOT 27290A-100000 AT sparkie DOT gnofn DOT org>
From: chambersb AT juno DOT com (Benjamin D Chambers)
Date: Mon, 03 Feb 1997 21:32:46 EST
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk


On Sun, 2 Feb 1997 23:46:21 -0600 (CST) "Colin W. Glenn"
<cwg01 AT gnofn DOT org> writes:
>On Sun, 2 Feb 1997, Jim Lefavour wrote:
>> > Warning! 8.3 programs will only see first occurance of file!
>> > 
>> Therein lies one problem with the lookup table approach - I have 
>seen 
>> several packages using long "Linux" filenames in TGZ files, which 
>use 
>> filenames that have large similar portions, viz.
>
>> open_file.c open_file.h open_file_mic.c open_file_mic.h
>
>Well, a tar program I'm using right now does a neat job of this, 
>they'd be
>named:
>
>> open_fil.c open_fi~.h open_fi'.c open_fi`.h
>
Unfortunately, I've tried this - and the files can't find each other
consequently (they have '#include "open_file.c"' not '#include
"open_fil.c"' et cetera).

>There's bound to be a dozen ways to skin this cat.
Unfortunately, I'm getting the feeling people will implement all of them
without a way for them to work together (that old song about 1200
different API's, none of which are compatible {that 1200 was a random
number - don't quote me :)})
               ^^^^
     Why Parentheses Get Messy :)


...Chambers