home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!sdd.hp.com!swrinde!gatech!destroyer!ncar!noao!amethyst!organpipe.uug.arizona.edu!news
- From: dave@cs.arizona.edu (Dave Schaumann)
- Newsgroups: comp.lang.c
- Subject: Re: Parameter passing & data abstraction
- Message-ID: <1993Jan1.063555.15299@organpipe.uug.arizona.edu>
- Date: 1 Jan 93 06:35:55 GMT
- References: <1992Dec30.184135.1963@organpipe.uug.arizona.edu> <24524@alice.att.com> <1993Jan1.002606.13612@organpipe.uug.arizona.edu> <D90-AWE.93Jan1044231@klara.nada.kth.se>
- Sender: news@organpipe.uug.arizona.edu
- Reply-To: dave@cs.arizona.edu (Dave Schaumann)
- Organization: University of Arizona
- Lines: 19
- In-Reply-To: d90-awe@klara.nada.kth.se (Assar Westerlund)
-
- In article <D90-AWE.93Jan1044231@klara.nada.kth.se>, d90-awe@klara (Assar Westerlund) writes:
- [comparisons deleted]
- >Better use size as Bjarne does. libg++ is usually compiled with
- >debugging-information included, which usually takes place on disk but
- >not in memory (unless you use a debugger, of course).
-
- Actually, physical size of the file is important too. Disk space may
- be cheap, but it's not free.
-
- Moreover, given an environment like a Sparc station with few users, 8
- or 16 megs of main memory and ~50 megs of swap space, the difference
- between 30K and 300K is not /that/ crucial.
-
- Fortunately, we're upgrading to 2.3 in a few days, so hopefully the
- point will become more academic (to me, anyway...)
-
- --
- Essentia non sunt multiplicanda praeter necessitatum -- William of Ockham
- (Fact need not be multiplied beyond necessity)
-