Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!nrl-cmf!ames!ucbcad!ucbvax!ulysses!hector!ekrell
From: ekrell@hector.UUCP
Newsgroups: comp.unix.wizards,comp.lang.c
Subject: Re: Motivation behind a particular piece of code in cpp
Message-ID: <3218@ulysses.homer.nj.att.com>
Date: Wed, 25-Nov-87 10:24:11 EST
Article-I.D.: ulysses.3218
Posted: Wed Nov 25 10:24:11 1987
Date-Received: Sun, 29-Nov-87 02:44:49 EST
References: <981@gumby.UUCP>
Sender: daemon@ulysses.homer.nj.att.com
Reply-To: ekrell@hector (Eduardo Krell)
Organization: AT&T Bell Labs, Murray Hill
Lines: 22
Keywords: cpp, static, STATIC
Xref: utgpu comp.unix.wizards:5230 comp.lang.c:5285

In article <981@gumby.UUCP> uday@mips.UUCP writes:

>   I do not understand the motivation behind a following declaration
>   found in the sources of cpp.
>
>     #define STATIC
>
>     Then there are various declartions of the sort
>     STATIC char ch.
>
>    If STATIC is defined to be null, why would one use it in declarations ?

My guess is that you could change the #define line to

#define STATIC static

and then make all those variables static without having to change
each individual declaration.
    
    Eduardo Krell                   AT&T Bell Laboratories, Murray Hill

    {ihnp4,seismo,ucbvax}!ulysses!ekrell