Function declarations

T. William Wells bill at proxftl.UUCP
Thu Sep 8 11:01:47 AEST 1988


In article <391 at pigs.UUCP> haugj at pigs.UUCP (The Beach Bum) writes:
: In article <697 at proxftl.UUCP> bill at proxftl.UUCP (T. William Wells) writes:
: >Well, consider the related question: who should have to deal with
: >the pain caused by systems that make one pass compilation
: >difficult: every user of ANSI C, or those people charged with the
: >writing of a C compiler for those systems?
:
: is this the claimed rational?  declaring functions as static local
: to a referencing function _can_ be handled with single pass compilation.
: the compiler may be easier to write than with that feature included,
: but with it included, the compiler could still be single pass.

The specific example they give is: a one pass compiler that
produces assembly code output and has to treat internal names
differently from external names.

The problem is that when first encountering the function name,
the compiler has to decide *right then* whether the name has
external linkage or not.

It's a rotten justification.

---
Bill
novavax!proxftl!bill



More information about the Comp.std.c mailing list