ANSI C -- static forward references

[Doug Gwyn]

In article <108 at decvax.UUCP> minow at 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.