From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newshunter!cosy.sbg.ac.at!newsfeed.Austria.EU.net!newsfeed.kpnqwest.at!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: <87u1rkl068.fsf@charter.net> <87wuwg1b05.fsf@photino.sid.rice.edu> <87ofhrc3ed.fsf@charter.net> <874rjj1ve1.fsf@photino.sid.rice.edu> <87it7yz2sf.fsf@photino.sid.rice.edu> <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> <87y9grsf <3225739210766179@naggum.net> <3C9A6917.FFC1C4ED@motorola.com> Mail-Copies-To: never From: Erik Naggum Message-ID: <3225746969252089@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 39 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 00:49:16 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1016758156 193.71.199.50 (Fri, 22 Mar 2002 01:49:16 MET) NNTP-Posting-Date: Fri, 22 Mar 2002 01:49:16 MET Xref: archiver1.google.com comp.lang.lisp:29801 * Paul Dietz | I am not kidding. I admit I am failing to penetrate your confusion. Oh, I see. You already know the one true answer, so bothering to read what I post is not necessary to you. | I suggest you look up the compiler optimization called 'software | pipelining'. Arrogant dipshit. | What I'm suggesting it just an application of that well-known technique, | which stretches out and overlaps iterations so as to avoid stalls. CAN YOU WORK IT OUT FOR PLISTS, TOO? YES OR NO? | In this case the alist algorithm can be more effectively pipelined | because it has more work off the critical path than the plist algorithm. No, this is simply _wrong_. Just get it, will you? | They are not the same, Mr. Naggum. The dependency between the CAR and | the CAAR is not on the critical path. Really? | We can wait several iterations between computing (CAR X) (for some cell | X) before we compute (CAAR X). We *cannot* do the same thing for the CDR | and the CDDR. Yes, it is _exactly_ the same thing. Why do you keep claiming this only for alists? You have not worked it out for plists, so you have no clue what you are talking about. What you have done for alists, can be done for plists. Just try it out, and you will see how simple this really is! /// -- 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.