In 20 you can do FileSystemError package and you get it. now we should work a lot to remove packageInfo and PackageOrganizer We will work (with ben) on the following scenario to offer a backward compatible solution:
the idea was:
when loading an MC package, this will be one RPacka of the name of the MC package.
For all the categories inside the MC pacakge, we use the rest as tags for the classes.
this means that
OpalCompiler-Core.mzc
--> one Package OpalCompiler-Core
tags
Bytecode Extras FrontEnd IR Semantics Translator
Now it means that it will take time to get rid of categories. Stef On Jun 16, 2012, at 5:57 AM, Sean P. DeNigris wrote:
"PackageOrganizer default packageOfClass: FileSystemError" returns the category, whether it's a separate package or not. How do I get the mc package?
The only thing I can think of is something like: MCWorkingCopy allInstances detect: [ :e | e packageName beginsWith: aString ] but it seems like there should be a built-in way, and the above is naive e.g. if aString = 'Package', the condition will be true for Package and PackageTests, which is wrong...
Thanks, Sean
-- View this message in context: http://forum.world.st/Finding-the-package-of-a-class-tp4635070.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.