Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mailrus!ames!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: extern question
Message-ID: <8200@brl-smoke.ARPA>
Date: 1 Jul 88 18:32:48 GMT
References: <4182@pasteur.Berkeley.Edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <4182@pasteur.Berkeley.Edu> faustus@ic.Berkeley.EDU (Wayne A. Christopher) writes:
>Is the following acceptable C code:

No.

>From an aesthetic viewpoint, I like to use extern anywhere I declare
>something but don't define it.  I think writing
>	int foo();
>for static functions is not as clear.

What you should have written was

	static int foo();

Aesthetics and proper use of the language have no necessary connection.