Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!nuchat!moray!urchin!p4694.f506.n106.z1.fidonet.org!Lynn.Lively
From: Lynn.Lively@p4694.f506.n106.z1.fidonet.org (Lynn Lively)
Newsgroups: comp.lang.c
Subject: Compressing C programs
Message-ID: <9242.25ABA802@urchin.fidonet.org>
Date: 8 Jan 90 19:26:21 GMT
Sender: ufgate@urchin.fidonet.org (newsout1.26)
Organization: FidoNet node 1:106/506.4694 - Fulcrum's Edge, Spring TX
Lines: 20

In an article of <7 Jan 90 04:13:07 GMT>, ferris@eniac.seas.upenn.edu (Richard T. Ferris) writes:

 RT>From: ferris@eniac.seas.upenn.edu (Richard T. Ferris)
 RT>Date: 7 Jan 90 04:13:07 GMT
 RT>Organization: University of Pennsylvania
 RT>Message-ID: <18731@netnews.upenn.edu>
 RT>Newsgroups: comp.lang.c
 RT>
 RT>I am interested in learning how to reduce the size of my TurboC
 RT>programs.  The .exe files are 13K even for very simple programs.
 RT>Could someone send me some suggested references?  Thanks.

 Richard,
     Are you using the integrated environment? If so, the default is to have
Debugging turned on. If you are using the command line check your  
configuration file. You may have -v specified in it which will give you  
Debugging each time you compile. The Debugging option burns up alot of space.
 Your Servant,
      Lynn