On Nov 15, 2004, at 2:00 PM, Christopher C. Stacy wrote:

>    In-Reply-To: <[EMAIL PROTECTED]>
>    References: <[EMAIL PROTECTED]> 
> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> 
> <[EMAIL PROTECTED]>
>    Cc: mikel evins <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
>          [EMAIL PROTECTED]
>    From: mikel evins <[EMAIL PROTECTED]>
>    Date: Mon, 15 Nov 2004 13:42:39 -0800
>    Sender: [EMAIL PROTECTED]
>
>
>
>    On Nov 15, 2004, at 12:12 PM, Arthur Lemmens wrote:
>
>> Mikel <[EMAIL PROTECTED]> wrote:
>>
>>> Again, the big missing features seem to be Unicode support and
>>> Win32 support.
>>
>> If "Win32 support" means "runs on Win32 systems", then I think CLisp
>> has both Unicode and Win32 support.  If "Win32 support" means "a 
>> usable
>> interface to a reasonable subset of the Win32 API", my impression is
>> that no open source Lisp has this.  (But I've never used CLisp or SBCL
>> or CMUCL, so please ignore me if I'm talking nonsense.)
>
>    What it means is, 'runs on Win32 and provides a means of calling 
> native
>    Win32 APIs.'
>
>    There is some concern about the speed of CLISP. We did some kind of
>    hairy things on the original SK8 to make sure that certain things 
> were
>    fast.
>
>    Turns out that CMUCL does run on Win32, it's just that the version 
> that
>    does is not yet released. We are in active conversations with the
>    person doing the port, and it looks like the features we need are
>    coming soon.
>
>    --me
>
>
>    In-Reply-To: <[EMAIL PROTECTED]>
>    References: <[EMAIL PROTECTED]> 
> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> 
> <[EMAIL PROTECTED]>
>    Cc: mikel evins <[EMAIL PROTECTED]>, [EMAIL PROTECTED],
>          [EMAIL PROTECTED]
>    From: mikel evins <[EMAIL PROTECTED]>
>    Date: Mon, 15 Nov 2004 13:42:39 -0800
>    Sender: [EMAIL PROTECTED]
>
>
>
>    On Nov 15, 2004, at 12:12 PM, Arthur Lemmens wrote:
>
>> Mikel <[EMAIL PROTECTED]> wrote:
>>
>>> Again, the big missing features seem to be Unicode support and
>>> Win32 support.
>>
>> If "Win32 support" means "runs on Win32 systems", then I think CLisp
>> has both Unicode and Win32 support.  If "Win32 support" means "a 
>> usable
>> interface to a reasonable subset of the Win32 API", my impression is
>> that no open source Lisp has this.  (But I've never used CLisp or SBCL
>> or CMUCL, so please ignore me if I'm talking nonsense.)
>
>    What it means is, 'runs on Win32 and provides a means
>    of calling native Win32 APIs.'
>
> How about: Corman, GCL, and ECL?

They're under discussion.

>
> I would also hope that it runs on the commercial Lisp systems.
> (I use Xanalys Lispworks.)

So would I. As I said, though, more Lisps == more missing features to 
implement. It would be good to get some basic level of function working 
on one Lisp, to begin with.

>
>    There is some concern about the speed of CLISP. We did some kind of 
> hairy
>    things on the original SK8 to make sure that certain things were 
> fast.
>
> I've heard that optimizing for CLISP is different than the kind
> of guesses that people usually make for compiled Lisp code.
>
>

It may be so. We'll talk it over.

--me


Reply via email to