>>> I don't know how widely used Object>>assert: is. Perhaps we >>> could have a different selector for that which takes a >>> block. >> >> I don't either, but I find strange the complete hierarchy of >> classes >> of Pharo having a method assert: available. Perhaps I'm >> blindfolded >> and Pharo and Squeak have found a wider use for assertions?
> Ah, sorry for the confusion. What I'm talking about here (and I > assumed > Alexandre was as well, but I could be mistaken) is indeed the use of > #assert: or some other message to test runtime invariants. So you'd > put > something like: [...] This is exactly what I had in mind I regularly use assert: to describe invariant, pre and postcondition. This complement testing pretty well in my opinion. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
