[rspec-devel] Where to start?

Matthias Hennemeyer mhennemeyer at googlemail.com
Thu Dec 4 10:44:52 EST 2008


I've created a ticket:
http://rspec.lighthouseapp.com/projects/5645/tickets/625-describe-with-ruby-19-should-include-an-enclosing-module-into-the-blocks-scope




Am 02.12.2008 um 15:49 schrieb David Chelimsky:

> On Tue, Dec 2, 2008 at 3:25 AM, Matthias Hennemeyer
> <mhennemeyer at googlemail.com> wrote:
>> Hi,
>> i want to restart rspec development.
>> Is there actually any particularly important area?
>> Is eg performance still an issue?
>> Would you point me somewhere?
>
> Hey Matthias,
>
> Thanks in advance.
>
> Performance and Ruby 1.9 compatibility are two key things I want to
> focus on in the coming weeks/months.
>
> One problem we have with 1.9 is the new scoping rules that make it  
> so that this:
>
> module Foo
>  module Bar
>    class Baz
>    end
>  end
> end
>
> module Foo
>  module Bar
>    describe "something" do
>      it "does something" do
>        baz = Baz.new
>      end
>    end
>  end
> end
>
> blows up on Baz.new. You have to say Foo::Bar::Baz.new to get it to
> work. I'd really like to figure out a way to discover the module scope
> in which #describe is declared and include that module within the
> ExampleGroup.
>
> There are others as well.
>
> And there are 240+ open tickets at
> http://rspec.lighthouseapp.com/projects/5645, so feel free to find any
> that interest you and patch away.
>
> Cheers,
> David
>
>> Thanks
>> Matthias
>> _______________________________________________
>> rspec-devel mailing list
>> rspec-devel at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rspec-devel
>>
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel



More information about the rspec-devel mailing list