Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!lll-crg!lll-lcc!well!ptsfa!gilbbs!mc68020
From: mc68020@gilbbs.UUCP
Newsgroups: net.sources.bugs
Subject: Re: Using identifiers with more than 7 chars. #$%@
Message-ID: <46@gilbbs.UUCP>
Date: Fri, 7-Mar-86 06:14:19 EST
Article-I.D.: gilbbs.46
Posted: Fri Mar  7 06:14:19 1986
Date-Received: Sun, 9-Mar-86 09:06:38 EST
References: <526@dsi1.UUCP> <2214@teddy.UUCP>
Distribution: net
Organization: Gil's Place, Santa Rosa CA
Lines: 56

In article <2214@teddy.UUCP>, jpn@teddy.UUCP writes:
> >[FLAME ON!]
> >
> >I  wish  that the people that post sources to the net would try to keep
> >in mind that some of us have compilers that can't swollow  indentifiers
> >that are longer than seven (7) characters long.
> 
> I cannot sympathize.  I have a program that was posted to the net some
> time ago called "shortc" which takes all conflicting long identifiers in
> a set of source files, and outputs #defines to differentiate them (which
> you can either insert into each source file, or into a header included
> by each file).  5 minutes work, and ANY program with long identifiers can
> be made to run.
> 
> Of course, if the pre-processor you have is ALSO limited to 7 characters,
> then you may STILL have a problem, since shortc assumes the preprocessor
> can differentiate all identifiers in the program.  Of course, if this is
> the case, I would throw away that compiler, and start over!
> 
> Of course, even with a bogus compiler, and a bogus preprocessor, you can
> still take the output of shortc and apply the changes by hand yourself!  The
> program will be less readable after this transformation, though.  No
> doubt shortc could be modified to output awk scripts, or something, to
> automate this process.
> 
> Is there enough interest to have this program re-posted to the net?
> 
> 
> John P. Nelson (decvax!genrad!teddy!jpn seismo!harvard!talcott!panda!teddy!jpn)




     *****GRRRRRRRRRRR*****

     In other words, John, you would have us believe that portability of code
is the responsibility *NOT* of the author(s), but the users?


     Yes, I would like very much to see your program, so that I can try to make
use of software written by inconsiderate louts who don't want to bother with
portability constraints.


(for the record, there is *NO* other C compiler available for my system)

-- 

====================================

Disclaimer:  I hereby disclaim any and all responsibility for disclaimers.

tom keller
{ihnp4, dual}!ptsfa!gilbbs!mc68020

(* we may not be big, but we're small! *)