[rspec-users] RSpec part of two (count 'em, two) GSoC projects

[Scott Taylor]

Some of you guys may know I thought about signing up for this.  I  
didn't sign up, because Rubinus seems to already have a pretty mature  
spec library (at least for core).  Why can't this be used for the  
other implementations?

Or is the focus on writing drivers for those implementations so that  
all of the specs can easily be run against multiple implementations?

I didn't understand this, nor how a VM works  (and still understand  
neither), so I ended up never signing up.  I even talked to David  
Black and he didn't have any insight on this point, so am I missing  
some big piece of the puzzle?

As far as I can tell, BDD should be used for development, hence the  
name Behaviour Driven *Development*.  So aren't these specs just  
going to be used to develop rubinus (mainly for the stdlib)?  Once  
these are mature, then the porting should be easy, shouldn't it?


Best,

Scott Taylor


On Apr 12, 2007, at 2:21 PM, David Chelimsky wrote:

> 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, talk about and contribute to RSpec!
>
> Cheers,
> David (on behalf the RSpec Development Team)
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users