The idea is that one day or later we will have to think about the benefit of pre and post condition. So assert: in object makes a lot of sense.
Now indeed it would be good that all the tests use assert: without block and use should: for that case. Stef On Oct 15, 2009, at 3:55 AM, [email protected] wrote: > > 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? _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
