Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Are there any Common Lisp implementations for .Net?

Are there any Common Lisp implementations for .Net?

like image 577
TraumaPony Avatar asked Sep 21 '08 07:09

TraumaPony


People also ask

Where is Common Lisp used?

Now it forms part of Google's travel industry department. In most cases, the company develops its software using Common Lisp. Another application in the transport sector is the London Tube that uses the software developed by Portuguese Siscog where Common Lisp is the main programming language.

What is a Lisp implementation?

Armed Bear Common Lisp (ABCL) is a full implementation of the Common Lisp language featuring both an interpreter and a compiler, running in the JVM. Originally started to be a scripting language for the J editor, it now supports JSR-223 (Java scripting API): it can be a scripting engine in any Java application.

Is Common Lisp compiled?

Lisp is a compiled general purpose language, in its modern use. To clarify: “LISP” is nowadays understood as “Common Lisp” Common Lisp is an ANSI Standard.

How old is Common Lisp?

Originally specified in 1958, Lisp is the second-oldest high-level programming language still in common use. Only Fortran is older, by one year. Lisp has changed since its early days, and many dialects have existed over its history.


1 Answers

I haven't looked at it recently, but at least in the past there were some problems with fully implementing common lisp on the CLR, and I'd be a little surprised if this has changed. The issues come up with things like the handling of floats where .net/clr has a way to do it that is a) subtly incorrect b) disagrees with the ANSI standard for common lisp but c) doesn't allow any way around this. There are other similar problems. This stuff is fiddly and perhaps not too important, but means you are unlikely to see an ANSI CL on the CLR.

There are bigger issues, for example common lisp has a more powerful object system, so you can't map it 1:1 to object in the runtime (no MI, for one). This is ok, but leaves you with an inside/outside sort of approach which is what a common runtime tries to avoid...

Whether or not you'll see a common lisp-ish variant running on it is a different story, but I don't know of any at the moment (not that I've looked hard)

like image 134
simon Avatar answered Sep 19 '22 13:09

simon