IronScheme turns One

By Michael Foord -
1.0 Beta 1 that is. Yesterday IronScheme 1.0 Beta 1 was released.

IronScheme is a rewrite of IronLisp, and aims to be an R6RS conforming implementation of Scheme based on the Microsoft Dynamic Language Runtime.

This new language implementation allows you to write .NET applications in Scheme or embed Scheme as a scripting language. It also opens up the possibility of Python and Scheme (and other dynamic languages) interoperating through the DLR.

This release includes a Visual Studio (SP1) plugin and is the creation of the author of the Open Source .NET xacc ide which has Scheme support.
From the 1.0 Beta 1 release notes:

Notably lacking for R6RS
  • call/cc only supports outward continuations
Differences
  • all raise's are continuable in the sense they can be caught
  • no tail calls in dynamic-wind
Extras
  • a generic load procedure for toplevel R6RS files
  • many extras procedures and macros in (ironscheme) library, mostly provided by psyntax
  • syntactic CLR integration, automatic conversion of closures into delegates
Credits
  • Abdulaziz Ghuloum and Kent Dybvig for psyntax (and friends)
  • Derick Eddington for making SRFI-1 R6RS compatible
  • Philip L. Bewig for SRFI-41
  • Marc Feeley for pretty-print
  • anyone else I missed
Planned to-do's (before final release)
  • testing of anything else
  • any additional CLR integration required
  • documentation
Updated (fixed/new)
  • Visual Studio 2008 SP1 plugin
  • A tiny MVC web framework
  • Added a lot of documentation, more to come
  • Many bug fixes
  • See 'Source Code' page for more details

Comments

Post a Comment

Popular posts from this blog

Extending Abobe Flash Player and AIR with Python and Ruby

By Michael Foord -
An intriguing blog entry about an Adobe experimental project. It is a C/C++ cross- compiler for the flash player and AIR. This means that you can (will be able to?) cross-compile the Python / Ruby/ lots of other language runtimes and then run them in Flash. The blog entry contrasts this approach to the DLR which requires the re-implementation of dynamic languages - hence IronPython and IronRuby. The project is already beyond proof-of concept, they even have Quake III cross-compiled and running in Flash. Extending Adobe Flash Player and AIR with C/C++ Cross-Compiler Quake 3 has already been ported to managed code , but this is even more impressive. Whether the Python interpreter can be cross-compiled to run on top of another runtime (with completely different basic types), without changing the language semantics at all, has yet to be proved - but it is a very interesting project. (It also means that Python/Ruby will possibly be enabled only by additional optional downloads - but don...
Read more

IronPython Tools for Visual Studio CTP3

By Michael Foord -
At PyCon this year Dino Veihland announced IronPython Tools for Visual Studio, an extension to Visual Studio 2010 for working with IronPython. It features Python syntax highlighting, awesome auto-complete (intellisense) and a host of other features for working with IronPython code in Visual Studio. It can be used with the free Visual Studio shell and doesn't require you to own a full copy of Visual Studio. The third CTP (Community Technology Preview) has been made available for download. IronPython Tools for Visual Studio We are happy to announce a minor update to the IronPython Tools for Visual Studio.  IronPython Tools for Visual Studio (IPyTools) is a set of extensions available for Visual Studio 2010 which supports development of IronPython applications.  This release is our 3rd Community Technical Preview (CTP) and builds upon the previous two releases.  The release is a minor update which includes bug fixes and a number of small features.  You can download...
Read more

Further Adventures of the Debugger

By Michael Foord -
Harry Pierson (Microsoft IronPython PM) has been experimenting with writing an IronPython debugger ( ipydbg ) on top of the .NET MDbg APIs. When we last left him , he had implemented Just My Code (JMC) support allowing you to step into IronPython code. Since then he has made a lot of progress including a colourful REPL (interactive console) and solving some difficult problems around getting to real values behind boxed IronPython variables (needed for showing local variables). He has blogged extensively on what he has been up to (more recent posts last): Showing Source Code Colorful Console IronPython ConsoleColorMgr (the colorful console code pulled out into a separate IronPython module) A Little Hack...err...Cleanup Getting Local Variables Displaying Values Command Routing Getting Arguments REPL Console A lot of functionality is now present. In the command routing entry Harry outlines the seven commands supported by the debugger so far: Continue, Quit, Show Stack Trace, Show Locals, ...
Read more