Well, the librelist archiver seems to swallow e-mail bodies when I send through squirrel mail (you can see them survive just fine if you read the messages through the rsync interface). So we'll test through Thunderbird and see how it goes. Anyway, I ran the tests for boson under rubinius and I got 12 errors related to argument_inspector.rb. The problem is that set_trace_func is not supported by Rubinius - it being a byte-code compiler and not so much of an interpreter as is the case with MRI. And the Rubinius debugger does not at first glance appear to be any kind of a substitute for the tracing approach of set_trace_func. What I've been unable to figure out is the value of scraping default values from method parameters. There is a substitute for scraping the parameters themselves - method#parameters but it's only supported for mri 1.9 and strangely enough for the latest stable rubinius. So the question is - does this by itself relegate boson to being an mri only framework? That's ok for me but I kind of like playing with Rubinius from time to time.
> Anyway, I ran the tests for boson under rubinius and I got 12 errors > related to argument_inspector.rb. This sounds like an issue. Could you repost most of the details you've mentioned as a github issue? > So the question is - does this by itself relegate boson to being an mri > only framework? That's ok for me but I kind of like playing with > Rubinius from time to time. Ideally I would love to have boson running on every ruby. Realistically, it will only get addressed when it bites me. In the meantime, I encourage you and anyone else to look into lib/boson/inspectors/argument_inspector.rb, which is what needs to be updated for rubinius. Feel free to ask questions about boson innards.