Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!endor!mckeeman
From: mckeeman@endor.harvard.edu (William McKeeman)
Newsgroups: comp.lang.c
Subject: Re: MAJOR ANSI C FLAW (my opinion, of course)
Message-ID: <2997@husc6.UUCP>
Date: Wed, 14-Oct-87 12:54:02 EDT
Article-I.D.: husc6.2997
Posted: Wed Oct 14 12:54:02 1987
Date-Received: Fri, 16-Oct-87 00:50:49 EDT
References: <1132@gilsys.UUCP>
Sender: news@husc6.UUCP
Reply-To: mckeeman@endor.UUCP (William McKeeman)
Organization: Aiken Computation Laboratory
Lines: 20
Keywords: external names, length, bogosity to the max

In article <1132@gilsys.UUCP> mc68020@gilsys.UUCP (Thomas J Keller) writes:
>
>	   ******  S  I  X  ******  character double case external names!!!!!!
>...
>    I wish I knew how to contact the committee and propose that they fix their
>screwup.  Maybe someone who reads this will know, and pass it on.

Yeah, its a botch.  But its not clear how x3j11 could have done
otherwise since the culprit is ancient loaders.  How about defensive
programming?  For everything you want to share with outsiders, have
#include botch.h
where you place defines like
#define MyLovelyHandpickedName X00001

So long as everyone uses your botch.h only the loader will have to
see those ugly short names.
/s/ Bill
W. M. McKeeman      mckeeman@harvard.edu
105 Aiken Computation Laboratory
Harvard University, Cambridge MA   02138