Julian Fitzell wrote: > > It would be really nice to have *one* SUnit that worked everywhere > with only minor platform-dependent pieces (like Seaside) where > necessary. This would be much more sustainable than the forked > situation we have currently, but that's a whole different battle.
Yes. > Although now I've said it, why not just start from scratch? There's > not a lot of code there... implement something that works the way you > want, build it using Grease/Slime so we can port it easily to > everywhere else, and that's something Seaside could use (assuming it > was compellingly better). And suddenly we'd have a test framework that > *did* run everywhere with a common code base. Some months ago Niall Ross took over maintainership of SUnit. IIRC he had the blessing of the previous maintainers, who hadn't been able to actually do much with it in recent years. At ESUG in Brest, Niall was actively working on SUnit and talking to folks from various Smalltalk implementations to try to get stuff into the next "official" release that would make everyone happy. So there is work going on to attempt to make the situation better. I'd think you'd want to at least discuss this with Niall and look at what he's done before starting over from scratch. If what's there doesn't meet Pharo's needs, starting from scratch might be appropriate. But if there can be "one true SUnit" for all Smalltalk, that seems like a better answer. Regards, -Martin _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
