Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!decvax!linus!philabs!micomvax!musocs!mcgill-vision!mouse
From: mouse@mcgill-vision.UUCP (der Mouse)
Newsgroups: comp.lang.c
Subject: Re: Default storage classes outside functions
Message-ID: <566@mcgill-vision.UUCP>
Date: Tue, 9-Dec-86 04:46:53 EST
Article-I.D.: mcgill-v.566
Posted: Tue Dec  9 04:46:53 1986
Date-Received: Sun, 14-Dec-86 08:51:26 EST
References: <1092@spice.cs.cmu.edu> <307@cartan.Berkeley.EDU> <3644@utcsri.UUCP> <1063@ihdev.UUCP>
Distribution: net
Organization: McGill University, Montreal
Lines: 26

In article <1063@ihdev.UUCP>, pdg@ihdev.UUCP (P. D. Guthrie) writes:
> Something interesting that is in the text though is the way that the
> default sc-specifiers are assigned.  K&R state that the default is
> auto inside a function and *extern* outside.  It seems to be *static*
> in most C implementations these days.

I have to differ.  The following produce *three* different effects:

int x;
extern int x;
static int x;

(outside a function).  So the default is really neither - or both; it
has the visibility of extern with the memory allocation of static.

One thing VMS C did right, or at least better: globaldef and globalref,
presumably doing the obvious things.

					der Mouse

USA: {ihnp4,decvax,akgua,utzoo,etc}!utcsri!mcgill-vision!mouse
     think!mosart!mcgill-vision!mouse
Europe: mcvax!decvax!utcsri!mcgill-vision!mouse
ARPAnet: think!mosart!mcgill-vision!mouse@harvard.harvard.edu

[USA NSA food: terrorist, cryptography, DES, drugs, CIA, secret, decode]