On Apr 10, 2010, at 4:08 PM, Robert wrote: > Is there anything outstanding of the right scope for a summer of code > project? I am thinking of applying, and I really like rubinius's > approach as a ruby implementation. > Rob > > On Mar 29, 5:53 pm, rogerdpack <[email protected]> wrote: >> Might be worth it to create a rubinius SoC page and add it to the >> list:http://rubysoc.org/students >> GL. >> -rp
As rubinius approaches 1.0 over the next 2 weeks, we need to start getting it working on Windows. This would likely entail some refactoring of a few I/O classes to abstract out some platform-specific items. There are already one or two people poking at this (on forks) so there is the possibility of some collaboration. Getting rubinius to compile and run on Windows is about the right size for a summer project. Of course, there are other possibilities. Here's a short list... 1. Test gems containing C extensions against rbx. Modify/extend the C API as necessary to support these extensions. 2. Resync the FFI support with jruby and other ruby runtimes. Possibly convert some C extensions to using FFI instead of the C API. 3. Look at failing specs in rubyspec and fix the bugs/limitations exposed by those failures. 4. Poke through all of the libraries inside rubinius that are written in ruby. Look for "FIXME" tags or comments indicating that the code is ugly and needs some work. Fix it. I don't have a link, but there is a project page somewhere containing ideas for some longer-term issues. Perhaps someone else who knows a bit more can speak up. cr -- --- !ruby/object:MailingList name: rubinius-dev view: http://groups.google.com/group/rubinius-dev?hl=en post: [email protected] unsubscribe: [email protected] To unsubscribe, reply using "remove me" as the subject.
