Because we did not have the time (and nobody took the time to look at
the code
and write a report for us on the extensions and status of MC1.5 and
MC1.6)
This is on the pipeline like SUnit+ and KernelExtensions.
Now december is a ***terrible*** for researchers in France and I
cannot cut myself in more slices
than already done.
Stef
On Dec 3, 2008, at 10:20 PM, Keith Hodges wrote:
Stéphane Ducasse wrote:
Yes but when we load a package we load the package and its extensions
and in Pharo
we take care about that.
Stef
So why do you stick with a broken MC then?
Keith
_______________________________________________
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
