Ben Coman wrote
I believe #asClass itself was introduced for a use case to simplify Workspace "user interactive" Gofer scripts to retrieve and load Configurations.
Yes. But it's no longer necessary due to... Ben Coman wrote
extended Gofer with a method #configurationOf:
We already have this :) Gofer it ... configurationOf: 'MyCoolProject'; loadStable. So there is no conflict: 1. Use the new Gofer API in the workspace (or the Metacello one Christophe pointed out) 2. Handle dependencies like we did for decades prior to #asClass ;) 3. Remove #asClass before it poisons our beloved system!!! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Problem-with-asClass-usage-tp4818686p4818861.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.