extern identifier length
Moderator, John Quarterman
std-unix at ut-sally.UUCP
Wed Oct 29 04:25:16 AEST 1986
From: harvard!encore!vaxine!nw (Neil Webber)
Date: Tue, 28 Oct 86 09:52:37 est
> From: gwyn at brl.arpa (VLD/VMB)
> Date: Mon, 20 Oct 86 9:44:19 EDT
>
> If it doesn't support 32-character extern name uniqueness, it isn't POSIX.
> 1003.1 imposes requirements on a C implementation beyond those of X3J11.
>
While I'm 100% behind this idea, I have to ask the question "how did this
come to be?" As I recall, the major argument against providing longer
extern names in X3J11 was that it would preclude X3J11 conforming C
implementations on systems with restricted object file formats. Is it
now impossible to provide a POSIX conforming implementation on those
systems?
This is only a problem for implementations layered on top of an existing
OS. Being somewhat of a "young one", I haven't worked on any systems
with a 6-character extern limit. (Life is tough, isn't it?) However, I'd
be interested in knowing what systems suffer from this restriction, and
why it doesn't matter that a POSIX environment can't be provided under
those systems.
Neil Webber Automatix Inc. Billerica MA
{decvax,ihnp4,allegra}!encore!vaxine!nw
Volume-Number: Volume 8, Number 3
More information about the Mod.std.unix
mailing list