Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!ziggy!usfvax2!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.arch Subject: Re: Bloat costs Message-ID: <266A93A8.528F@tct.uucp> Date: 4 Jun 90 17:00:24 GMT References: <26798@eerie.acsu.Buffalo.EDU> <266576A7.6D17@tct.uucp> <25444.2667fff8@ccavax.camb.com> Organization: ComDev/TCT, Sarasota, FL Lines: 13 According to merriman@ccavax.camb.com: >In fact, a lot of our maintenance headaches are caused by scrimping >on resources ("Why use a longword here instead of a word? We'll >never see a value of more than a few thousand." Ha!). Such "scrimping" is often done in the name of saving memory. However, there are smarter ways to save memory, such as keeping only one record of a file in memory instead of the whole file, etc. Just because some programmers are penny wise and pound foolish does NOT mean that frugality is counterproductive. -- Chip Salzenberg at ComDev/TCT ,