A Whole Bunch of Stuff: Part I

By Michael Foord -
My backlog includes a lot of interesting snippets and blog entries that probably don't warrant a whole entry to themselves. There's a lot of good stuff in them, so I'm splitting them out into two separate entries.

A blog entry on using the IronPython 1 hosting API to call functions - including embedding it in ASP.NET pages.
This happened a while ago, but I missed it. Windows High Performance Computing Operating System is out (HPC Server 2008) - and it includes IronPython 'out of the box'!

"To tempt Unix users and coders in scientific programming languages, there is a built-in POSIX shell, support for IronPython, IronRuby and Fortran. Microsoft is also developing new tools such as the F# programming language and .NET Parallel Extensions."

"Much of the legacy code that developers may need to support is Linux-based, he says. Mendillo notes that support for Iron Ruby, Iron Python, Fortan and a built-in Posix-compliant shell should help many developers bridge to non-Windows environments."
I noted recently that the Intellipad tool, part of the Oslo framework, is scriptable with IronPython. Jon Flanders has a blog entry showing how to write new commands for IPad using IronPython.
One of the things I didn't mention in the recent entry on Silverlight 2 is that a version for Windows Mobile has been planned. The version of .NET targetting Windows Mobile (and the XBox 360) is the Compact Framework - and this doesn't include the 'Reflection.Emit' (code generation and introspection) APIs needed by the Dynamic Language Runtime. This unfortunately means that Silverlight 2 for Windows Mobile won't be able to run applications written in IronRuby or IronPython.
As the Dynamic Language Runtime forms the basis of both the IronPython and IronRuby projects (and currently slightly out of sync versions of the DLR are included in the downloads for both of these projects - making it hard to create projects that target both languages), and the DLR will be part of .NET 4, it really needs its own home. That home is a project page on the Codeplex Open Source project hosting site. This page is little more than a placeholder currently, but it notes:

"The Dynamic Language Runtime enables language developers to more easily create dynamic languages for the .NET platform. In addition to being a pluggable back-end for dynamic language compilers, the DLR provides language interop for dynamic operations on objects. The DLR has common hosting APIs for using dynamic languages as libraries or for scripting in your .NET applications. This project provides one stop shopping for the DLR components, our open source implementations of IronPython and IronRuby, documentation, and samples."

"This project is currently under construction, and we're targeting our first release of DLR v0.9 in November. We will be releasing simultaneously with IronPython v2.0. You can see all the DLR code in the IronPython Project's latest RC release and weekly source pushes. Our code is also available on IronRuby's site with daily source pushes."

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 the latest rel
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