Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!rutgers!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: ANSI C -- static forward references
Message-ID: <5455@brl-smoke.ARPA>
Date: Mon, 15-Dec-86 12:38:21 EST
Article-I.D.: brl-smok.5455
Posted: Mon Dec 15 12:38:21 1986
Date-Received: Wed, 17-Dec-86 18:52:50 EST
References: <108@decvax.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <108@decvax.UUCP> minow@decvax.UUCP (Martin Minow) writes
about the usage of "static" and "extern".

The interplay between "static" and "extern" was carefully worked out
to maximally support existing practice, while permitting one-pass
compilation implementations.  Martin's code example falls into the
"undefined" category, which means that an implementation is free to
provide the semantics that Martin wants, but that a portable
application cannot count on them.  I believe an editorial
clarification of this is in the works.

My feeling is that it would take a very strong argument to convince
X3J11 to change this aspect of the standard.