Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!cs.utexas.edu!uunet!mcsun!unido!horga!presto!dc
From: dc@presto.ruhr.de (David Channing)
Newsgroups: comp.sys.atari.st
Subject: Re: static globals? [addendum to previous message]
Message-ID: <8423444@presto.ruhr.de>
Date: 3 May 91 14:18:26 GMT
References: <1991Apr30.183034.15773@lsuc.on.ca> <1991May1.020731.16272@wam.umd.edu>
Lines: 13

In article <1991May1.020731.16272@wam.umd.edu> dmb@wam.umd.edu 
(David M. Baggett) writes:
> 
> If you're not using separate compilation; i.e., if you have one
> giant .c file or #include everything all at once, then static
> vs. auto makes little difference for globals.

Unless of course your global variable names conflict with names in the 
library, in which case you would want to make them static.

--
dc@presto.ruhr.sub.org
dc@presto.ruhr.de