InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Releases: JRuby 1.1.2; New Preview of Ruby 1.8.7

Posted by Werner Schuster on May 28, 2008

Sections
Development,
Architecture & Design
Topics
JRuby ,
Java ,
Runtimes ,
Programming ,
Ruby
Tags
JRuby ,
Open Source Project Releases ,
Ruby1.9
Just in time for RailsConf 2008JRuby 1.1.2 was released  (download JRuby 1.1.2 versions).  This maintenance release in the 1.1.x branch consists of bug fixes and some major performance increases.

The startup performance boost (reported previously), is based on the idea to put JRuby .jar files into the bootclasspath - loading classes from the bootclasspath than from the regular classpath is faster because the bytecode doesn't get verified.

Another Ruby runtime release is available in the stable Ruby 1.8.x branch of MRI. Ruby 1.8.7 preview 4 has been released. You can see a rough list of features and API added since 1.8.6 or the full Changelog for MRI.

A quick diff of the new features in Ruby 1.8.7 preview 4 and previous previews, shows some activity and some previously introduced features disappeared and changed again.

A big change is the re-appearance of Symbol#to_proc. The feature made it's first appearance in Ruby 1.9. Ruby 1.8.7 preview 1 included a backported version - which was quickly discovered to break software using their custom versions of Symbol#to_proc, in particular Rails.  This caused the feature to be pulled - and now it's back, after the behavior was changed to comply with the test suite. As it seems now, Symbol#to_proc seems to be here to stay in Ruby 1.8.7.

Here's a list of further API changes not mentioned previously:
  • Binding#eval
  • __method__  which returns the name of the current method as a Symbol
  • String#bytesize returns the size of the string in bytes
  • Object#instance_exec
The behavior of a few APIs was changed, which might cause some applications to break:
  • Date.parse was changed so that  '##.##.##' is now interpreted as 'YY.MM.DD'  instead of 'MM.DD.YY'.
  • String#to_i, String#hex and String#oct changed the behavior for the underscore '_' character in number strings, eg '1__0'.to_i in Ruby 1.8.6 was turned into '10', but in Ruby 1.8.7 it is turned into '1'. See the release notes for a more complete overview.

No comments

Watch Thread Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.