Re: What are the domains that lisp doesn't fit int?
- From: Pascal Bourguignon <pjb@xxxxxxxxxxxxxxxxx>
- Date: Sat, 28 Apr 2007 02:16:32 +0200
Dan Bensen <randomgeek@xxxxxxxxxxxxxx> writes:
fireblade wrote:
What are ... domains where lisp doesn't fit in?
Drivers: close to the metal.
If lisp worked perfectly well as system programming language on the
lisp machines, what does that say on the ability of lisp for writting
drivers?
Common Lisp doesn't prevent an implementation to have implementation
specific extensions to be able to run on the bare metal, even on an
Intel processor. See Movitz.
Embedding: Poor memory resources.
If lisp worked on systems of 50 years ago, what does that say on the
memory resources needed by lisp?
The Common Lisp specification is lax enough to allow a very small
implementation, not counting even the subsets of Common Lisp that are
explicitely allowed. Have a look at the various LIMIT variables!
Limit Minimal value
--------------------------- -------------
ARRAY-DIMENSION-LIMIT 1024
ARRAY-RANK-LIMIT 8
ARRAY-TOTAL-SIZE-LIMIT 1024
CALL-ARGUMENTS-LIMIT 50
CHAR-CODE-LIMIT 96
LAMBDA-PARAMETERS-LIMIT 50
MULTIPLE-VALUES-LIMIT 20
--
__Pascal Bourguignon__ http://www.informatimago.com/
Nobody can fix the economy. Nobody can be trusted with their finger
on the button. Nobody's perfect. VOTE FOR NOBODY.
.
- Follow-Ups:
- Re: What are the domains that lisp doesn't fit int?
- From: George Neuner
- Re: What are the domains that lisp doesn't fit int?
- References:
- What are the domains that lisp doesn't fit int?
- From: fireblade
- Re: What are the domains that lisp doesn't fit int?
- From: Dan Bensen
- What are the domains that lisp doesn't fit int?
- Prev by Date: Re: checking implementation defined and implementation dependent behaviour
- Next by Date: Re: function from string
- Previous by thread: Re: What are the domains that lisp doesn't fit int?
- Next by thread: Re: What are the domains that lisp doesn't fit int?
- Index(es):