Path: utzoo!attcan!uunet!world!esegue!compilers-sender
From: pardo@june.cs.washington.edu (David Keppel)
Newsgroups: comp.compilers
Subject: Re: Managing Symbol Tables on Floppy Disk
Keywords: design, storage
Message-ID: <13147@june.cs.washington.edu>
Date: 26 Sep 90 23:06:02 GMT
References: <1990Sep18.140940.29483@NCoast.ORG>
Sender: compilers-sender@esegue.segue.boston.ma.us
Reply-To: pardo@june.cs.washington.edu (David Keppel)
Organization: University of Washington, Computer Science, Seattle
Lines: 16
Approved: compilers@esegue.segue.boston.ma.us


ramsey@NCoast.ORG (Cedric Ramsey) writes:
>[Maintaining a symbol table on floppy]

This doesn't solve your problem:

One of my compilers profs told of a PC COBOL compiler that looked at
the amount of available memory and used different algorithms and
storage layouts depending on the configuration.  This seemed pretty
clever at first, then seemed pretty gross because several versions
would have to be maintained.  Then it seemed pretty clever because
they solved their problem: as fast as possible for the given machine.

	;-D oN  ( War stories?  Nah, a low-intesity conflict )  Pardo
-- 
		    pardo@cs.washington.edu
    {rutgers,cornell,ucsd,ubc-cs,tektronix}!uw-beaver!june!pardo
-- 
Send compilers articles to compilers@esegue.segue.boston.ma.us
{ima | spdcc | world}!esegue.  Meta-mail to compilers-request@esegue.