Thanks for the help guys. Actually I thought of having something as simple as
aClass isSystemDefault
we could do it at the class level I think that we should get some static metadata soon or later
then having more control detecting changes (to system or user objects). One may implement in a browser a Warning mode that prevents/protect from mistakes, once I've implemented an extension method in Behavior with the **same selector** of an existing method, and the tools didn't helped me to detect it.
Another use case is for helping future tools to know which changes to track.
Hernán
2010/9/1 Stéphane Ducasse <stephane.ducasse@inria.fr>:
In scriptLoader you get the list of all the core packages with version. I will start to play with metacello to do that instead of doing everything :)
On Aug 31, 2010, at 10:29 PM, Hernán Morales Durand wrote:
Hi guys,
Given any Pharo image and a (any) package or class category, how do you find if the package/class category belongs to the official image release? Thanks,
Hernán
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project