Please mark them as expected failures but do not remove them because they show the real semantics of closure.
Stef On Jul 5, 2009, at 2:11 PM, Lukas Renggli wrote: > ClosureTests>>#testToDoOutsideTemp and > ClosureTests>>#testWhileModificationBefore demonstrate two minor > problems with the closure implementation. Many Smalltalk > implementations (including the expensive industrial strength ones) get > these two and some of the other tests in ClosureTests wrong. > > If these two tests cannot be easily fixed I don't think they are a > show stopper and should be marked as expected failures. I don't know > about the other closure tests. > > Cheers, > Lukas > > > 2009/7/5 Adrian Lienhard <[email protected]>: >> Hi Eliot and Lukas >> >> There are 9 failing tests in the two classes ClosureCompilerTests and >> ClosureTests that you wrote. >> >> Do they document bugs in the implementation, and if yes, what needs >> to >> be done? >> >> Thanks, >> Adrian >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
