Re: compiled open source Windows lisp (was Re: Python becoming less Lisp-like)

2005-03-22 Thread TLOlczyk
On 16 Mar 2005 06:37:45 -0500, Carl Shapiro <[EMAIL PROTECTED]> wrote: >I have a virtually completed port of CMUCL to Win32. And, if I was >not busy organizing a Lisp conference, it would be publicly available >by now. If it's the conference I think, then the deadline for papers was about a week

Re: compiled open source Windows lisp (was Re: Python becoming less Lisp-like)

2005-03-16 Thread Brandon J. Van Every
Carl Shapiro wrote: > "Brandon J. Van Every" <[EMAIL PROTECTED]> > writes: > >> Last I looked, 2 years ago?, there were no compiled, open source >> lisps that ran on Windows. Has this changed? > > I have a virtually completed port of CMUCL to Win32. [etc] Ah, so you're the brave lad I heard abou

Re: compiled open source Windows lisp (was Re: Python becoming less Lisp-like)

2005-03-16 Thread Carl Shapiro
"Brandon J. Van Every" <[EMAIL PROTECTED]> writes: > Last I looked, 2 years ago?, there were no compiled, open source lisps that > ran on Windows. Has this changed? I have a virtually completed port of CMUCL to Win32. And, if I was not busy organizing a Lisp conference, it would be publicly ava

Re: compiled open source Windows lisp

2005-03-15 Thread Brandon J. Van Every
Christopher C. Stacy wrote: > > All this information has been available in FAQs and > on many web pages since forever. When I Google for "comp.lang.lisp FAQ," I get a document that was last updated in 1997. Consequently I do not pay attention to it. I do peruse newsgroup archives, and I did make

Re: compiled open source Windows lisp (was Re: Python becoming less Lisp-like)

2005-03-15 Thread David Golden
James Graves wrote: > > But coverage in this area (compiled CL) is a bit thin, I'll admit. > But who really cares? After all, there are the mature commercial proprietary lisp compilers for those people who insist on using closedware OSes, and they've already proven they're willing to use close

Re: compiled open source Windows lisp (was Re: Python becoming less Lisp-like)

2005-03-15 Thread Christopher C. Stacy
"Brandon J. Van Every" <[EMAIL PROTECTED]> writes: > Last I looked, 2 years ago?, there were no compiled, open source > lisps that ran on Windows. Has this changed? GCL (formerly known as KCL and ACL) has been around since 1984, and has been available on Windows since 2000. ECL (another KCL deri

Re: compiled open source Windows lisp (was Re: Python becoming less Lisp-like)

2005-03-15 Thread James Graves
Brandon J. Van Every <[EMAIL PROTECTED]> wrote: >James Graves wrote: >> >> If you want to do application development, Common Lisp is where it's >> at, no doubt about it. There are more and better libraries for CL >> these days, and they are easier to install and manage with tools like >> ASDF. Mul

Re: compiled open source Windows lisp

2005-03-15 Thread Edi Weitz
On Tue, 15 Mar 2005 23:29:04 +0100, Fraca7 <[EMAIL PROTECTED]> wrote: > I don't think so. I recently (about 2 months ago) started to want to > learn Lisp (didn't go far for now) and wanted to find a Windows > impl, to evaluate "cross-platformability". The only open source/free > software Lisp inte

Re: compiled open source Windows lisp (was Re: Python becoming less Lisp-like)

2005-03-15 Thread Fraca7
On Tue, 15 Mar 2005 12:25:02 -0800, Brandon J. Van Every wrote: > Last I looked, 2 years ago?, there were no compiled, open source lisps that > ran on Windows. Has this changed? I don't think so. I recently (about 2 months ago) started to want to learn Lisp (didn't go far for now) and wanted to

compiled open source Windows lisp (was Re: Python becoming less Lisp-like)

2005-03-15 Thread Brandon J. Van Every
James Graves wrote: > > If you want to do application development, Common Lisp is where it's > at, no doubt about it. There are more and better libraries for CL > these days, and they are easier to install and manage with tools like > ASDF. Multiple open-source implementations, covering the most p