Alright, so here we are. I'd like to start things off with a post
about the status of Cardinal, in parts:
1: The Parser. The parser is broken. We know this. It's also slow. I
expect that the parser is where most of the serious work is going to
have to go. In particular, I've been trying to wrap my head around the
assignment thing. I expect to write another message to this list soon
about how I expect to make it work.
2: The object model. The object model doesn't quite match Ruby's, and
should be fixed. In particular, I'd like to see us actually implement
the chart shown on the RDoc for Class. Should also fix things so that
class methods have a good place to go via metaclasses made when a
class is made. (This may already be happening to some degree, I'm not
sure.)
3: A related issue that'll probably come on the tails of that last
one: Method Resolution Order. Perl6 and Python both use C3, but Ruby
does not. We're going to need to ensure that our MRO follows this
diagram:
http://phrogz.net/RubyLibs/RubyMethodLookupFlow.png
4: The stdlib. Joeri and Danius have been doing good work on this
front. I also recently found out about Rubinius (
http://rubini.us/), a
project to make a new Ruby VM. It also implements its stdlib entirely
in Ruby, which may be of great value to us. I'd love to see us be able
to make use of what they've already done.
So. Welcome to the list. Thoughts anyone?
-- treed