From ...
Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news.mailgate.org!newsfeed.icl.net!newsfeed.esat.net!nslave.kpnqwest.net!nloc.kpnqwest.net!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail
Newsgroups: comp.lang.lisp
Subject: Re: data hygiene [Re: Why is Scheme not a Lisp?]
References: <gat-1203021200230001@eglaptop.jpl.nasa.gov> <87u1rkl068.fsf@charter.net> <87wuwg1b05.fsf@photino.sid.rice.edu> <87ofhrc3ed.fsf@charter.net> <874rjj1ve1.fsf@photino.sid.rice.edu> <b84e9a9f.0203141902.24ce7c85@posting.google.com> <87it7yz2sf.fsf@photino.sid.rice.edu> <sfwr8mlewux.fsf_-_@shell01.TheWorld.com> <87d6y5heq2.fsf@becket.becket.net> <87elilwsnx.fsf@photino.sid.rice.edu> <87u1rfn07o.fsf@becket.becket.net> <87k7sbtzp5.fsf@photino.sid.rice.edu> <871yej1v0h.fsf@becket.becket.net> <3225566321428508@naggum.net> <3C97C8EA.38FFD47A@motorola.com> <3225571208798099@naggum.net> <3C9806B8.B239D290@interaccess.com> <3225694232096978@naggum.net> <3C99D8D6.CA34A3D6@interaccess.com> <3225739029050571@naggum.net> <sfwk7s5o7gy.fsf@shell01.TheWorld.com> <gat-2103021907160001@192.168.1.50> <41yedf67z.fsf@beta.franz.com>
Mail-Copies-To: never
From: Erik Naggum <erik@naggum.net>
Message-ID: <3225771981784501@naggum.net>
Organization: Naggum Software, Oslo, Norway
Lines: 18
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 22 Mar 2002 07:46:08 GMT
X-Complaints-To: newsmaster@KPNQwest.no
X-Trace: nreader1.kpnqwest.net 1016783168 193.71.199.50 (Fri, 22 Mar 2002 08:46:08 MET)
NNTP-Posting-Date: Fri, 22 Mar 2002 08:46:08 MET
Xref: archiver1.google.com comp.lang.lisp:29833

* Duane Rettig <duane@franz.com>
| We should look at this carefully, Erann.  It is possible you are
| measuring the wrong thing here.  [...]
: 
| If my guesses are correct, then what you have is a highly optimized
| version of assoc (possibly even open-coded) and a non-optimized getf,
| which at least has optional processing.

  This is why I wrote my own alist-get and plist-get and even wrote the
  tagbody out in full and tweaked it considerably.  The overhead of using
  assoc and getf with all their (hugely different) generality completely
  wipes out any savings in memory access unless the lists are _really_
  long, as in: _way_ beyond the threshold at which to switch to hashtables.

///
-- 
  In a fight against something, the fight has value, victory has none.
  In a fight for something, the fight is a loss, victory merely relief.