On 2012-06-22, at 09:39, Esteban Lorenzano wrote:
> me neither. a=b is clear enough for me. If I want more detail, I add a
> description.
> but perhaps I'm loosing something that I'm not seeing.
>
> Esteban
error messages + inspect???
I hate to go and re-eavluate the code to see what was wrong during comparison...
like that you keep the two arguments somewhere up in the stack and you can go
and simply go and see what went wrong.
consider
self assert: self someExpressionReturningFalse = self
someExpressionReturningTrue
how the heck do you know what went wrong?
assert:equals: is the thing to use.
I don't like it particularly, it feels too java-ish, I prefer much more the
"shoulder"
framework written in bern.
self someExpressionReturningFalse should = self someExpressionReturningTrue
ˆˆˆˆˆˆ
that somehow feels much more natural to me :P
