> Ah, OK. I guess it's really a question of perception. not perception. Just money. Give me three engineers full times during two years and you will not recognize pharo :)
> The world in which I work is a bit different from the wonderful world of > Pharo (no sarcasm intended!), in that we can't ship *anything* unless *all* > our tests are green. The concept of "expected failures" just has no place, > because as long as there are failures we still have work to do. Oh this is easy we can remove tests and your customers will be happy :) Now some tests represents the semantics of blocclosure that no smalltalk truly implement, so this would be a pity to throw them away. > I can understand Doru's description of an expected failure as a kind of > bookmark, to be added and discarded during the day, but I get a bit nervous > that the sight of too much green might make me miss the fact that I'm not > finished yet :-p Exact this is why removing expected failures at the start of each cycle is the thing to do _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
