[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
ECL - more details please!
- To: donc@ISI.EDU
- Subject: ECL - more details please!
- From: Giuseppe Attardi <attardi@DI.UniPi.IT>
- Date: Thu, 13 Jan 94 02:29:52 +0100
- Cc: firstname.lastname@example.org
- In-reply-to: Don Cohen's message of Wed, 12 Jan 94 15:49:14 -0800 <9401122349.AA15502@hpai19.isi.edu>
- Organization: Dipartimento di Informatica - Universita' di Pisa - Italy
Date: Wed, 12 Jan 94 15:49:14 -0800
Posted-Date: Wed, 12 Jan 94 15:49:14 -0800
From: donc@ISI.EDU (Don Cohen)
I'd appreciate more details, such as:
- How large is the image?
The kernel without compiler is 700KB, with compiler and some
preallocated memory 2MB.
- How conformant is it to CLtL1, CLtL2, proposed Ansi CL?
It is fully CLtL1 conformant. It has a CLtL2-conformant CLOS.
- What are the limitations on heap size, stack size, etc.?
Those of your machine: heap is obtained with sbrk, the stack is the C
- Does it do its own paging or must everything fit in main memory?
(This question only applies to OS's like DOS that don't do this
It relies on the OS for paging: on DOS it uses go32.
- Is it able to call DOS/UNIX programs (like CLISP)?
Definitely: either through a direct function call or through the Lisp
function (SYSTEM string).
- Does it contain any support for screen windows, as described in
- Does it contain any support for window systems such as MSWindows,
I have a specially optimized version of CLX.
- Does it compile into native machine instructions or use a byte
It compiles to C and then uses the C compiler on your machine to generate