------art_60899_17316194.1170618707262
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Well, you can solve that problem by overriding method_missing on Object so
that expectations that match the regex /^not_(.+)/ can be automagically
negated...

I'm kidding of course. I applaud this decision by the RSpec team. A couple
of Rails projects that I work on use RSpec and at one point, also used
Mocha. Some subtle bugs were cropping up due to clashes between the
libraries' use of method missing.

Mushfeq.

On 2/4/07, Jim Weirich <jim / weirichhouse.org> wrote:
>
> Klaus Ramelow wrote:
> > David Chelimsky schrieb:
> >> Dear spec'ers,
> >> deprecated methods.
> >> (see below).
> >> be going and what you should use instead.
> >>
> >>
> > I would prefere instead (as logical expressions): equal   /   not_equal
> > so:
> > actual should not_equal(expected)
>
> By grouping the not with the should, you are able to negate arbitrary
> expectations.  If the not goes with the expectation, then each
> expectation must provide its own negative (e.g. equal/not_equal,
> match/not_match).
>
> -- Jim Weirich
>
> --
> Posted via http://www.ruby-forum.com/.
>
>

------art_60899_17316194.1170618707262--