[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: &REST
- To: Common-Lisp@sail.stanford.edu
- Subject: Re: &REST
- From: K. Shane Hartman <SHANE@JASPER.PALLADIAN.COM>
- Date: Fri, 15 May 87 13:03 EDT
- In-reply-to: <8705142119.AA04811@bhopal.edsel.uucp>
- Reply-to: K. Shane Hartman <SHANE%JASPER@LIVE-OAK.LCS.MIT.EDU>
Date: Thu, 14 May 87 14:19:29 PDT
From: edsel!bhopal!jonl@navajo.stanford.edu (Jon L White)
...
But the kinds of folks who have tolerated the bug which Dan Wienreb so
gloriously announced are not entirely stupid. There is a market, at
least amongst some systems programmers who use lisp, to get the kind of
"last-bit tweaking" performance that a stack-allocated &rest list would
afford. Lucid's product will shortly be giving the user access to some
of the underlying primitives which permit dynamic-extent consing (the
3600's "stack list" consing is one such example).
...
In fact, we use stack allocated &REST lists exclusively. We tried using heap
allocated &REST lists and found that it significantly impaired the performance of at
least one large system. I think lisp vendors should be encouraged to provide this
sort of feature.
-[Shane]->
- References:
- Re: &REST
- From: edsel!bhopal!jonl@navajo.stanford.edu (Jon L White)