rubydoes.net

John Lam has released revision 93 to SVN. This new release now passes 1541/2468 specs (62%). Click here to see the output of all the tests.

The highlights from the commit logs :

• r89 Minor updates to Ruby to support hosting in ASP.NET
• r93 A bunch of String specs have were re-enabled since we no longer crash when parsing them
• A bunch of regex functionality (still using .NET regex) is enabled - =~, sub,gsub etc. are now implemented in this release.
• There was a split in the way the DLR is organized. Microsoft.Scripting.Core.dll is the DLR, and Microsoft.Scripting.dll are where libraries like the Math libraries for the DLR will live from now on.

To view the complete set of commit comments click here

Seo Sanghyeon also updated the HOWTO and patches for working with IronRuby from within Mono.

John Lam has also mentioned that since the release of r93 he has bee working heavily on String, specifically the parts of String required for running Rails. He reports 70% of String required to run Rails is passing!

Thanks again to the IronRuby team, both inside and outside Microsoft for their hard work!

John Lam has posted revision 85 to SVN. Here are the commit comments

————————————————————————
r86 | jlam | 2008-03-24 19:51:39 -0400 (Mon, 24 Mar 2008) | 4 lines

Finished refactoring the Rakefile.
Fixed two bugs that blocked the specs from passing - one was RUBY_VERSION not de
fined as a MutableString and the other was treating $~ as read-only.

rake spec should report 1325 examples with 0 failures. Will check in a new revis
ion that resets the baseline using new features shortly.
————————————————————————

The specs are passing again! Here is the complete output. A diff shows that dir#tell specs have been removed, but 2 new examples are passing in fixnum and 2 more new examples are passing in string. Great job guys, thanks IR team!

John Lam has posted a few new revisions to SVN. Here are the commit comments for 79-84

————————————————————————
r78 | jlam | 2008-03-18 16:43:49 -0400 (Tue, 18 Mar 2008) | 1 line

removing stuff that was accidentally added in previous revision
————————————————————————
r79 | jlam | 2008-03-20 09:32:10 -0400 (Thu, 20 Mar 2008) | 1 line

Simple commit to get to a clean svn status
————————————————————————
r80 | jlam | 2008-03-20 11:23:29 -0400 (Thu, 20 Mar 2008) | 1 line

Removing rubytesthost (is renamed IronRuby.tests in current sources).
————————————————————————
r81 | jlam | 2008-03-21 00:43:26 -0400 (Fri, 21 Mar 2008) | 1 line

This build is an interim build that compiles and has basic tests passing. There
were a lot of renames etc. that happened here, as well as new features. There’s
also a lot of new Rake infrastructure in this build that works well enough to push
stuff out and compile in different contexts. There will be another build tomorrow
that will fix more issues.
————————————————————————
r82 | jlam | 2008-03-21 00:47:21 -0400 (Fri, 21 Mar 2008) | 1 line

Updated initializer.
————————————————————————
r83 | jlam | 2008-03-21 09:47:52 -0400 (Fri, 21 Mar 2008) | 1 line

Fixed some problems in the Rakefile to try and solve the build in arbitrary path
scenario. Note VS build is broken in this revision.
————————————————————————
r84 | jlam | 2008-03-21 10:23:05 -0400 (Fri, 21 Mar 2008) | 1 line

Fixes external build. rake compile should now work from arbitrary directories.
VS build still broken.
————————————————————————

At least 1 spec is broken in this revision so no update to specs, yet.

For some reason I have been lax in promoting the interesting IronRuby links from around the internet. Here is a new list of links, and expect weekly posts like this in the future.

Martin Maly has a set of posts for building a language on the DLR. Really interesting stuff, and he walks our through the ToyScript language that ships with IronPython.

Ivan Porto Carrero posted an update on his upcoming book, IronRuby in Action. Ivan also posts about a good looking IDE theme for Ruby in Steel, and building IronRuby and Mono in Leopard.

Michaeldotnet had posted a nice IronRuby getting started post months ago. Since then, he moved his blog to here, and posted some great stuff like semi practical IronRuby, and details about the zlib library he is writing in pure ruby.

Paul Ferrill walks through a WPF app written in IronRuby.

MSDN Blogs has a long list of DLR sites and resources within Microsoft.

Steve Eichert posted about getting started with IronRuby. If you get caught by the same compile issue he did when compiling via rake, these threads on the mailing list are talking about it. 1, 2

Lastly an oldie that I had missed, Cory Fox posted about some of the internals of IronRuby and walks through some of how IronRuby compiles and runs under the covers.

Ruby In Steel is a full featured Ruby IDE plugin for Visual Studio .net. It provides lots of great features for Ruby developers, and lots of shortcuts for Ruby on Rails developers. Ruby in Steel provides a very nice Ruby/Rails development experience.

The guys responsible for Ruby in Steel are also working on IronRuby in Steel. Still in the very early stages of the product, but it shows lots of promise, and already includes a visual form designer.

The installer also allows the user to install packages like rails, and mysql, great for those just getting started with Ruby. I didn’t happen to have rails installed on this VM, and the installer worked perfectly installing both IronRuby in Steel and Rails. IronRuby in Steel provides all the normal options of Ruby on Steel text edition, but also adds 2 new project types, IronRuby console app and IronRuby forms app. The experience is what you would expect as well. I started a new forms app, dragged a button onto the form, and then double clicked on the button. I was brought to the code where I was greeted with

Well, I added the button1.text = “changed” . Clicked Ruby Run, and my IronRuby forms app was running. Great start, and I would recommend anyone interested in doing more IronRuby, or even Ruby should look at Ruby in Steel’s suite of products, or their IronRuby product specifically.

The IronRuby team committed revision 77 into RubyForge. Here is the commit comment :

Big set of changes from our Silverlight push. Things that are working here should be rudimentary debugging in VS under Desktop CLR.

Also the beginnings of our integration work with the latest build of Ruby specs (hence the explosion in # of files under tests). The older stuff will be removed once we get the new specs working.

This revision still won’t let you do a Silverlight build yet- that will come later.

The spec results for this revision can be found here, but don’t appear to have changed since R76.

I missed a couple revisions, but 76 was posted last week. Here are the svn logs. rake compile was not working for me before the newest rev, but with this newest one rake compile worked first shot. Also remember to run rake -T to see all the juicy rake options the IronRuby team has built thus far. More to come soon

————————————————————————
r74 | jlam | 2008-01-23 13:32:07 -0500 (Wed, 23 Jan 2008) | 12 lines

Drive spec failures to zero through exclusions.

We now run all specs with the exception of those contained in Kernel, Module, Fi
le, Thread, and MatchData directories. These contain random errors that cause th
e harness to blow up, and will be fixed in the future. For the time being, this
should be sufficient to integrate into SNAP.

- Run all specs via “rake spec” with exception of types noted above.
- Added new reporters to auto-generate exclusions based on failed specs: “rake s
pec io - gen_excludes” will generate exclusions for all IO class tests.
- Added gap analysis tool “rake gap foo [args to foo]” - this will give you a li
st of methods that we don’t implement, but are required to run foo. Note that ga
p tool requires compiling ironruby.libraries.scanner which is written using C# 3
.0 (rake compile does not compile this by default).
- Enabled rudimentary Regex support to enable tests to pass
- Added warning infrastructure via “-w” switch which redirects correctly to new
IO infrastructure.

(Shelveset: SpecFixes13;REDMOND\jflam | SNAP CheckinId: 1877)

————————————————————————
r75 | jlam | 2008-01-26 16:13:31 -0500 (Sat, 26 Jan 2008) | 3 lines

Adding Peter Bacon Darwin’s Range patch.

You can use “rake spec” to run all specs now. You can also use “rake spec range”
to just run the specs for Range.
————————————————————————
r76 | jlam | 2008-02-11 14:16:38 -0500 (Mon, 11 Feb 2008) | 5 lines

A number of changes in this push:

- Warning message about using globals for locals
- Beginnings of work on fixing the scanner (not much visible in this change toda
y)
- Large number of ongoing DLR refactoring related changes
————————————————————————

Cory Foy posted a very in depth post explaining how to call Ruby from within .net. This post is much more then just code, it really digs deep into how IronRuby is working under the covers, very informative! Cory describes a bit on how the RubyEngine is working under the covers, and how the AST (abstract syntax tree) plays into the execution. Much like Cory, though, I was unaware that the ?? operator has been added to .net 3.0, and that’s great. (c#)?? == (ruby)||= Get it?

On a related note, Phil Haack also updated the wiki with a sample on executing Ruby in .net here.

krishna figured out that you can build with the shipping rakefile if you provide an explicit path to MERLIN_ROOT to rake. Use :

rake compile MERLIN_ROOT=c:pathtoironrubytrunk

Worked perfectly for me. Thanks!

Seo Sanghyeon has put together a nant build which is by far the easiest way to build the new drop of IronRuby. Download this nant file and put it in the src folder, and then just run nant. If you do not have nant yet, get it here. Once you run this build file, you will have a new rbx.exe and Ruby.dll in the same src folder.

The newest drop did not come with a sln file. John Lam noted that he needs to create one, but for now here is one I put together. The first step is to get this sln file, and put it in the root of the IronRuby project where the RakeFile is. The next step is to download this zip file of replacement csproj files, and then replace the proj files in the src and utils folders with the included ones.

I had to replace those proj files because they were being signed and the key was not provided. I thought about doing it all with a new key, but that would have required new proj files as well, so now signing has been removed from all the projects. With this solution you can open, edit, F5, and debug the newest drop, at least until the team prepares a proper set of proj and sln files.