Support for %i{} and %I{} #2269

Closed
wants to merge 2 commits into
from

4 participants

@LTe

No description provided.

@dbussink
Rubinius member

Isn't this a 2.0 feature?

@LTe

Isn't this a 2.0 feature?

Hm... yes. Should I only change guard on specs?

@dbussink
Rubinius member

Well, there are a few issues. First of all we need to get the parser for 2.0 in general. We don't want to be changing the 1.9 parser to add adhoc 2.0 features to it.

We also need a place in Rubinius to implement 2.0 features, like we have 1.8 and 1.9 stuff now as well in the kernel for example. The problem here however is that the 1.9 -> 2.0 difference is much smaller than 1.8 -> 1.9, so using the same strategy as 1.8 -> 1.9 could result in a lot of duplicate code.

The specs also need to be guarded with 2.0 guards then. They always need to pass if you run them with MRI 1.9.3, and also 2.0. Personally I always first write specs while running against MRI, before implementing stuff in Rubinius to make sure to always set them up correctly for the right MRI version.

@brixen
Rubinius member

I'll be working on the Ruby 2.0 parser in the 3.0 branch of https://github.com/rubinius/rubinius-melbourne.

@brixen brixen closed this Apr 19, 2013
@mhenrixon

Any progress on this? It is holding us up

@brixen
Rubinius member

@mhenrixon I've been fixing up the parser and compiler specs so I can work on new syntax. Should be soon.

@mhenrixon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment