David Chelimsky:
>> RSpec 1.2.9 adds ./lib and ./spec (from the project root) to the load
>> path. So it sounds it's loading your custom 'set' before the one in
>> stdlib.
That would explain that backtrace. Thanks for the clarification!
>> I've run into load order problems like this before, and
On Sat, Oct 10, 2009 at 10:16 PM, David Chelimsky wrote:
> On Oct 10, 2009, at 5:54 PM, Shot (Piotr Szotkowski) wrote:
>
>> It seems RSpec 1.2.9 is be breaking my specs in an interesting way
>> (both under Ruby 1.8.7 and 1.9.1). The problem may very well be in
>> my non-standard approach to monkey
On Oct 10, 2009, at 5:54 PM, Shot (Piotr Szotkowski) wrote:
It seems RSpec 1.2.9 is be breaking my specs in an interesting way
(both under Ruby 1.8.7 and 1.9.1). The problem may very well be in
my non-standard approach to monkey-patching core/stdlib classes,
but my approach does work with RSpec