Newsgroups: comp.lang.dylan,comp.lang.misc,comp.lang.lisp,comp.object,comp.arch
Path: cantaloupe.srv.cs.cmu.edu!europa.chnt.gtegsc.com!news.mathworks.com!gatech!news.uoregon.edu!news.bc.net!info.ucla.edu!library.ucla.edu!csulb.edu!csus.edu!netcom.com!NewsWatcher!user
From: hbaker@netcom.com (Henry Baker)
Subject: Re: allocator and GC locality, and locality generally (was Re: cost of malloc)
Message-ID: <hbaker-3107951036070001@192.0.2.1>
Sender: hbaker@netcom15.netcom.com
Organization: nil
References: <9507261647.AA14556@aruba.apple.com> <3vac07$ptf@info.epfl.ch> <3vb382$dtr@jive.cs.utexas.edu> <3vbl70$bht@fido.asd.sgi.com> <3vbrrf$ege@jive.cs.utexas.edu> <3vc8kj$52l@fido.asd.sgi.com>
Date: Mon, 31 Jul 1995 18:36:07 GMT
Lines: 13
Xref: glinda.oz.cs.cmu.edu comp.lang.dylan:4929 comp.lang.misc:22406 comp.lang.lisp:18491 comp.object:36073 comp.arch:59995

In article <3vc8kj$52l@fido.asd.sgi.com>, mikemac@engr.sgi.com (Mike
McDonald) wrote:

>   Yep. According to this professor, compiler construction is only about
> parsing
> with error recovery. Maybe a little pinhole optimization too.
                                      ^^^^^^^

Make that 'pinhead' optimization [something that Zippy would do, e.g.].

-- 
www/ftp directory:
ftp://ftp.netcom.com/pub/hb/hbaker/home.html
