From: Friedrich Dominicus
Subject: Re: Difference between free and commercial implementations of CL
Date:
Message-ID: <87llvu613h.fsf@fbigm.here>
Jan Rychter <···@rychter.com> writes:
> I'm interested in opinions from users who have chosen a commercial
> implementation of CL instead of using a free one [1]. I'm particularly
> interested in people using UNIX systems, where there are at least three
> excellent free implementations: CMUCL, CLISP and SBCL. If you use
> Allegro CL or LispWorks, why?
What prevents you from using both?
I prefer LispWorks because of it whole IDE aspect, there is CAPI and
many other libraries. The price is reasonable and I want to have Lisp
vendors.
>
> The reason I'm asking is that I'm a little puzzled: on one hand, CMUCL
> seems to fullfill most of my needs as far as CL programming is
> concerned. On the other hand, I hear people saying that Allegro CL is
> the only reasonable option. If it is so, I'd like to know why.
Allegro has probably the most libraries. Just check what they have put
into the "free" section of their homepages.
>
> As an example, I've found CMUCL a little faster on my programs than the
> evaluation version of Allegro CL. But Allegro seems to have a better
> inspector facility, which helps in debugging. Also, it comes with lots
> of well-organized documentation. Then there is LW, which comes with a
> GUI, but since I use XEmacs, it isn't overly useful to me.
Well you can still use LispWorks with Emacs, and you can still use CAPI.
Regards
Friedrich
Friedrich Dominicus <·····@q-software-solutions.com> wrote in message news:<··············@fbigm.here>
...
> I prefer LispWorks because of it whole IDE aspect, there is CAPI and
> many other libraries. The price is reasonable and I want to have Lisp
> vendors.
...
>
> Regards
> Friedrich
>
Talking about Lispworks....
I just tried to set up Lispworks Personal Edition 4.2 (free) on a
fresh Suse Linux system (8.2) and Lispworks dies with something like:
Error: FIND-NAMED-WIN32-PROC-IN ......
I have read somewhere else that it is not working with glibc versions
later than 2.3.1-6. Is there a fix other than re-installing 2.3.1-5
and adjusting LD_LIBRARY_PATH ?
-klaus
From: Edi Weitz
Subject: Re: Difference between free and commercial implementations of CL
Date:
Message-ID: <87he6iqv4m.fsf@bird.agharta.de>
··········@yahoo.de (Klaus Momberger) writes:
> Talking about Lispworks....
>
> I just tried to set up Lispworks Personal Edition 4.2 (free) on a
> fresh Suse Linux system (8.2) and Lispworks dies with something
> like:
>
> Error: FIND-NAMED-WIN32-PROC-IN ......
>
> I have read somewhere else that it is not working with glibc
> versions later than 2.3.1-6. Is there a fix other than re-installing
> 2.3.1-5 and adjusting LD_LIBRARY_PATH ?
You might want to ask on the LW mailing list or ask Xanalys
directly. I think this'll increase your chance of getting an answer
(soon).
Cheers,
Edi.
From: Dan Corkill
Subject: Re: Difference between free and commercial implementations of CL
Date:
Message-ID: <3EF5B7F9.1000205@attbi.com>
> You might want to ask on the LW mailing list or ask Xanalys
> directly. I think this'll increase your chance of getting an answer
> (soon).
Indeed. I had a solution from Xanalys for running LWPE on Redhat 9.0
several hours after I sent them an inquiry... Superb response for
a not-yet-paying user!
From: Espen Vestre
Subject: Re: Difference between free and commercial implementations of CL
Date:
Message-ID: <kwfzm1xlte.fsf@merced.netfonds.no>
··········@yahoo.de (Klaus Momberger) writes:
> I have read somewhere else that it is not working with glibc versions
> later than 2.3.1-6. Is there a fix other than re-installing 2.3.1-5
> and adjusting LD_LIBRARY_PATH ?
I don't think adjusting LD_LIBRARY_PATH won't suffice, you need to
use the alternate clib's linker/loader.
LW 4.3 will fix this, according to the Xanalys FAQ database.
And debian has fixed it (by reintroducing a depreciated symbol) in
2.3.1-8, so you may consider using debian instead of Suse.
I'm very happy with using debian (in different versions) with LW.
--
(espen)
From: Espen Vestre
Subject: Re: Difference between free and commercial implementations of CL
Date:
Message-ID: <kwadc9xloq.fsf@merced.netfonds.no>
··········@yahoo.de (Klaus Momberger) writes:
> I have read somewhere else that it is not working with glibc versions
> later than 2.3.1-6. Is there a fix other than re-installing 2.3.1-5
> and adjusting LD_LIBRARY_PATH ?
I don't think adjusting LD_LIBRARY_PATH will suffice, you need to
use the alternate clib's linker/loader.
LW 4.3 will fix this, according to the Xanalys FAQ database.
And debian has fixed it (by reintroducing a depreciated symbol) in
2.3.1-8, so you may consider using debian instead of Suse.
I'm very happy with using debian (in different versions) with LW.
--
(espen)
Espen Vestre <·····@*do-not-spam-me*.vestre.net> wrote in message
....
> I don't think adjusting LD_LIBRARY_PATH will suffice, you need to
> use the alternate clib's linker/loader.
>
right...
> LW 4.3 will fix this, according to the Xanalys FAQ database.
>
> And debian has fixed it (by reintroducing a depreciated symbol) in
> 2.3.1-8, so you may consider using debian instead of Suse.
> I'm very happy with using debian (in different versions) with LW.
>
thanks for the response. For various reasons I would like to stay
with SuSe, so I will probably just wait for the new LWPE release.
regards,
-klaus