Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!yetti!geac!daveb
From: daveb@geac.UUCP
Newsgroups: comp.lang.c
Subject: Misconceptions re ansi c flaw
Message-ID: <1639@geac.UUCP>
Date: Mon, 19-Oct-87 13:50:06 EDT
Article-I.D.: geac.1639
Posted: Mon Oct 19 13:50:06 1987
Date-Received: Mon, 19-Oct-87 23:31:09 EDT
References: <1132@gilsys.UUCP> <1246@bsu-cs.UUCP> <6543@brl-smoke.ARPA> <123@sdeggo.UUCP> <31140@sun.uucp>
Reply-To: daveb@geac.UUCP (Dave Collier-Brown)
Organization: The little blue rock next to that twinkly star.
Lines: 27

In article <31140@sun.uucp> guy%gorodish@Sun.COM (Guy Harris) writes:
>Once more: the adoption of the ANSI C standard will not force ANY C
>implementations to limit themselves to 6-character one-case external names.
>Anybody out there who still believes this should stop doing so.
>	Guy Harris
>	{ihnp4, decvax, seismo, decwrl, ...}!sun!guy
>	guy@sun.com

  I'd like to emphasize what Guy just said, and add my own comment
to the effect that linkers can and have been extended transparently
to all programs __except__ those actually calling
restricted-name-length fortran subroutines/functions.  
  One of the disfeatures of a news system using asnychrony and
flooding is that misconceptions sometimes propagate faster than
valid data.

 --dave (sigh) c-b

ps: Last week I posted a scenario to the above discussion showing
how a certain large, stingy company upgraded their linkers.  If it
didn't reach your site, I'd appreciate hearing from you by mail.  I
live near a news-eating black hole, you see...
-- 
 David Collier-Brown.                 {mnetor|yetti|utgpu}!geac!daveb
 Geac Computers International Inc.,   |  Computer Science loses its
 350 Steelcase Road,Markham, Ontario, |  memory (if not its mind)
 CANADA, L3R 1B3 (416) 475-0525 x3279 |  every 6 months.