Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!necntc!ima!haddock!karl
From: karl@haddock.ISC.COM (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: C pointer problems in VMS.
Message-ID: <3121@haddock.ISC.COM>
Date: 22 Mar 88 23:25:32 GMT
References: <12464@brl-adm.ARPA> <25667@cca.CCA.COM> <3072@haddock.ISC.COM> <25834@cca.CCA.COM>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 17

In article <25834@cca.CCA.COM> g-rh@CCA.CCA.COM.UUCP (Richard Harter) writes:
>>(Also, I consider it bad practice to declare a function with local scope, so
>>I'd put it outside main() anyway, even if nobody else calls it.)
>
>Consider me confused.  What do you mean by declaring a function with
>local scope?  Are you saying that you are a one-function per file advocate
>or that one shouldn't declare static functions?

Neither.  I'm saying that I consider
    main() { extern void p(); p(); }
to be inferior to
    extern void p();
    main() { p(); }
Like it or not, the function "p" DOES have at least file scope, so you might
as well declare it that way.

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint