BT

Your opinion matters! Please fill in the InfoQ Survey!

Lisp on the .NET Runtime

| by Jonathan Allen Follow 195 Followers on Oct 26, 2007. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

Continuing our coverage of Lisp, we present some of the efforts underway to port the venerable language to the .NET runtime. Variants we look at include IronLisp, LispSharp, and Common Larceny.

IronLisp is new project loosely based on Scheme. It is being developed against the Dynamic Language Runtime, or DLR, an extension for the Common Language Runtime that adds features needed for dynamic languages like Python and Ruby. As the DLR is relatively new and very much in flux, this decision is an additional burden to the IronLisp team.

IronLisp is not currently Scheme compatible, but Llewellyn Pritchard writes:

Ideally IronLisp at some future time, will support/comply to some degree of Scheme, or will have a compatibility mode, or have macros to make it syntax (and functionally) compatible. With this in hand, hopefully IronLisp would be capable of running Scheme libraries.

Llewellyn Pritchard was inspired in part by Rob Blackwell's LSharp .NET. This lisp dialect is similar to Arc and is considered stable. An example of using Windows Presentation Foundation with LSharp is available.

Currently there is not much activity on the LSharp project and no mention of DLR or SilverLight support.

Another older project for the CLR is Common Larceny. Part of the Larceny Project, it is a Scheme implementation based on Twobit compiler. Though mired in the alpha stage, there is active work on the project with the last release in July. It explicitly states that it is not supported on Mono at this time.

With no production grade Lisp that is compatible with Common Lisp or Scheme, Lisp on the .NET platform does not seem to be a viable option at this time. Though the DLR may drive new interest over the coming year, for now it seems Lisp developers wanting access to the .NET framework should stick to compatibility layers like RDNZL.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT