Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!henry
From: henry@utzoo.UUCP (Henry Spencer)
Newsgroups: net.lang.c
Subject: Re: C and ANSI Standard
Message-ID: <4260@utzoo.UUCP>
Date: Wed, 22-Aug-84 14:15:51 EDT
Article-I.D.: utzoo.4260
Posted: Wed Aug 22 14:15:51 1984
Date-Received: Wed, 22-Aug-84 14:15:51 EDT
References: <12598@sri-arpa.UUCP>
Organization: U of Toronto Zoology
Lines: 34

> I want flexnames (arbitrary-length identifiers) everywhere you can use
> an identifier in C, particularly external names.  I would settle for
> some large length, like 80.  I WON'T settle for 6 or 8, and I don't
> care how many linkers will have to be rewritten to accomodate it.

This has already been discussed to death.  Flexnames, no.  Longer limits,
where practical, yes.

> If this isn't done, then the standard will be a joke, and no piece of
> VAX 4.2 or Sun code will ever run anywhere else.

I don't know about the first part, but  the second part is
probably true already .

> Also, if anybody is contemplating making structure member names be
> unique (that is,
> 
> struct foo {
>     int a;
> };
> 
> struct bar {
>     int a;
> };
> 
> being illegal) please stop them from doing so.  Please don't let the
> ANSI standard be a mediocre version of V7 Unix C!

The draft says, I believe, that member names are local to the structure
they are declared in.  So the above is legal.  Note that it's legal in
V7 C too, but for different and much sleazier reasons.
-- 
				Henry Spencer @ U of Toronto Zoology
				{allegra,ihnp4,linus,decvax}!utzoo!henry