<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV>There's another quirk I wanted to bring up. It's about the failure message with should_equal and should_be.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>x.should_equal 2</DIV><DIV>a.should_not_be nil</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>When they fail they yield messages like:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>1 should equal 2</DIV><DIV>nil should not be nil</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>When I'm caught off guard, which can be often, these messages confuse me. 1 should equal 2? No it shouldn't. nil should not be nil? But they are the same!</DIV><DIV>You get my drift? When taken out side the context of a specification, these statements are just absurd.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>In my humble opinion, these messages should include their context and read like this:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>x should equal 2 but was 1</DIV><DIV>a should not be nil but was nil</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I realize there might be an issue printing the expression that gets evaluated, but you guys have done some cool magic to this point. Have you got a bit more up your sleeves?</DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>Micah Martin</DIV><DIV>8th Light, Inc.</DIV><DIV>www.8thlight.com</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR class="Apple-interchange-newline"></SPAN> </DIV><BR></BODY></HTML>