> Hi all, > > updated MIME, URI and File packages in inbox. ok
> Some of the URI related changes are somewhat incomplete as I merged > them > from a different context. Hopefully I didn't break anything though :-) > > With merges like this it is really a problem that MC doesn't allow > cherry picking changes... but you cannot reject a change? > The overall goal with the URI changes is to complete replace the > current > Url implementation. Do we keep around the Url class so that people can load their code? May be we could have a general mechanism for having class deprecation? > We have done this quite successfully in Sophie and > even more radically in the experimental ySqueak branch. > > Suggesting to replace Url classes by URI was a sure way to get a flame > war going on the Squeak dev list. I imagine that we are less knowgeable. > So what is general opinion on this for > Pharo? Not really. what could be the argument? Stef > > > Michael > > _______________________________________________ > 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
