Displaying 4 results from an estimated 4 matches for "rubinus".
Did you mean:
rubinius
2007 Apr 12
6
RSpec part of two (count ''em, two) GSoC projects
Here is the list of Ruby related projects accepted for GSoC. It
includes two very similar projects (seemingly the same project,
really, but I''m not saying anything ;) ) using RSpec to build a spec
suite for implementations of the Ruby language:
http://code.google.com/soc/ruby/about.html
I''m, personally, very excited about the implications of this. Thanks
to all of you who use,
2008 Apr 24
4
Pure Ruby HTTP parser
...s going to be
PAINFULLY slow on MRI. That''s not the point :)
I thought I''d try out writing out a Ruby version of the parser for the
purposes of Rubinius. For those of you who aren''t aware, Ragel supports a
goto-driven FSM on Rubinius by injecting assembly directly, and Rubinus head
honcho guy Evan Phoenix is working on a patch for Ragel to update it to the
new compiler semantics. So really, there is a purpose for trying this out.
Anyway, here''s my initial hack. It''s nasty, and presently jams the entire
FSM into instance-specific data. Aieee! But it...
2007 Mar 24
1
spec''ing metaprograming & rails CRUD
...sed for the following:
1. Verification of Code Working the way you expect it to. This is
more fine grained, and better suited to Test::Unit, although the code
can easily break after refactoring.
2. Documentation
3. Test-First development. What small piece do I implement next?
(Think of the Rubinus/private methods example)
4. Defining Behaviour, which of course, is simply high level
verification on exposed methods.
Thoughts on these matters?
Scott
2007 Mar 24
0
Using spec fixtures with integration tests
...Verification of Code Working the way you expect it to. This is
> more fine grained, and better suited to Test::Unit, although the code
> can easily break after refactoring.
> 2. Documentation
> 3. Test-First development. What small piece do I implement next?
> (Think of the Rubinus/private methods example)
> 4. Defining Behaviour, which of course, is simply high level
> verification on exposed methods.
>
>
> Thoughts on these matters?
>
> Scott
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 24 Mar 20...