Date: Mon, 3 Feb 1997 23:18:46 -0600 (CST)
From: "Colin W. Glenn" <cwg01 AT gnofn DOT org>
To: Benjamin D Chambers <chambersb AT juno DOT com>
cc: opendos AT mail DOT tacoma DOT net
Subject: Re: [opendos] OpenDOS + Win95 w/FAT32? 
In-Reply-To: <19970203.183342.4575.4.chambersb@juno.com>
Message-ID: <Pine.GSO.3.95.970203231323.6130E-100000@sparkie.gnofn.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-opendos AT mail DOT tacoma DOT net
Precedence: bulk

On Mon, 3 Feb 1997, Benjamin D Chambers wrote:
> >> 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).

I can see where that would be a bummer, unless you construct a proofreader
program which would go through all the sources, comparing the includes it
finds with a 'capture file' (contains the realname and resulting name)
editing the lines to match the resulting world.  (ugly as it is)

> >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 

Then the best thing to do is to keep hashing this out until we can agree
as to where to start skinning the cat and work from there. 

 /\  /\
( o)(o )
== <> ==

ansi artist I'm not.