"The language is still changing, there is no spec for the language, there are going to be differences between implementations that are essentially undefined behavior."
The Register has an article about Ruby.NET with a lot of quotes from the project manager, John Lam, such as the one above. However, the spec is not something they can do anything about, so they have no choice. But one that caught my eye was one they do have some choice over:
Some familiar features will not be implemented, however. "Call with current continuation, we're not implementing that. [Although] JRuby isn't either.
...
It makes me ask myself a couple of questions, but not being familiar with Ruby or
call/cc (Score:1)
Re: (Score:1)
They aren't necessary if you have the precise set of control structures that you really need built into your language. That's slightly different from what you said.
As for the Nickclarkulator's second question, Larry's put in a fair bit of work to make sure that it's possible to host a Perl 6 implementation without exposing continuations. Part of that may have been the desire to get Perl 6 running on the Pe
Re: (Score:1)
Wait, does that mean PerlŠ6 itself does not have continuations?
Re: (Score:1)
I think (and Larry's really the one to ask here) that the goal is to support as much of the specification tests as possible without requiring continuations. They're still in the language though.
No "callcc" in Ruby 2.0? (Score:1)
http://lambda-the-ultimate.org/node/1801 [lambda-the-ultimate.org]
Web Frameworks (Score:2)