In leiu of our meeting this week, here is a quick status update in the form of a blog entry. With my talk last week, I admit I didn’t make as much progress as I may have hoped, and this week and next will be a little hectic with tests in both of my classes.
Last Week
Ruby 1.9
I took a little time out to look into Ruby 1.9 a little bit more, just to get a feel for what I might be missing here. Matz’s Google TechTalk was informative, and gave me a little better idea of what had changed.I’ve also started looking a bit through the code for Ruby 1.9, particularly the parser, to see what has changed here. I’ve only started looking, but at it’s core I believe I can still use the same technique with few changes that I’m using in 1.8, so that is good news.
Parser/Unparser Progress
I’ve also finished looking through most of the test results, and I think I’m down to the last few items outstanding, namely figuring out the details of regular expression options. (Interesting to note that the regular expression engine changed in Ruby to Oniguruma, but the documentation for this is better, and I think any changes to this for Ruby 1.9 should be pretty straight forward.)
Documentation
Finally, I’ve added a couple of blog entries, and also created a wiki page for Ruby on the compiler wiki with links to some blog entries about performance, as well as the concurrency article I had sent to you from InfoQ, and links to the various implementations. I wasn’t sure where to attach this page, so right now it is just floating in the wiki. I could attach it to the References page, which is probably the most appropriate place, though I wasn’t sure really how to categorize it.
This Week
I’ll be working on getting the pretty-printing underway, first changing to a simplified ATerm form for things like function definitions, which are pretty complicated and then using the pretty printer to do the work to get it back into Ruby code.