Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!cs.utexas.edu!uunet!twwells!bill From: bill@twwells.com (T. William Wells) Newsgroups: comp.lang.c Subject: Re: Uninitialized externals and statics. Message-ID: <1989Aug19.053711.7462@twwells.com> Date: 19 Aug 89 05:37:11 GMT References: <2128@infmx.UUCP> <10764@smoke.BRL.MIL> <478.nlhp3@oracle.nl> Organization: None, Ft. Lauderdale, FL Lines: 20 In article <478.nlhp3@oracle.nl> bengsig@oracle.nl (Bjorn Engsig) writes: : The default initialization of statics and externals without explicit inital : values also has the advantage (at least on some systems) that the load : module will be smaller. If you explicitly initialize to zero, all those : zeroes will be stored in the file. At one point, we got toasted by some of our customers because our executables were excessively large. It seems that one of our programmers did things like: int Array[1000] = {0}; This sort of thing made the difference between a product that could be shipped on one floppy and one that required two. Guk. --- Bill { uunet | novavax | ankh | sunvice } !twwells!bill bill@twwells.com