Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!rutgers!clyde!burl!codas!ki4pv!tanner From: tanner@ki4pv.UUCP (Tanner Andrews) Newsgroups: comp.lang.c Subject: Re: Re: ANSI C -- static forward references Message-ID: <6927@ki4pv.UUCP> Date: Sat, 20-Dec-86 18:36:54 EST Article-I.D.: ki4pv.6927 Posted: Sat Dec 20 18:36:54 1986 Date-Received: Sun, 21-Dec-86 09:36:55 EST Organization: CompuData South, DeLand Lines: 17 Summary: The "extern" isn't needed -- leave it off! While no doubt many people consider it good and fine to say something like the following example fragment, I find that the assorted compilers for our assorted machines all work just as well or better if you omit the storage class on the forward reference. That "extern" just isn't needed. Why not leave it off. Makes the code more accurate (seeing that "blunge" really ISN'T extern). Also, no harm results if "blunge" moves to another module! All in all, better to just leave off the "extern" entirely! /* start of example */ extern char *blunge(); /* declare blunge */ char *gork() { return(blunge(69)); } /* use blunge */ static char *blunge(arg) int arg; { /* body of blunge here */ } /* end of example */ --Tanner Andrews