[Pharo-project] Pool dictionary cause problems to load package from monticello
nicolas.cellier.aka.nice at gmail.com
Sun Apr 17 08:55:05 CEST 2011
VW uses generalized namespaces.
A PoolDictionary is simply a Namespace, just as Smalltalk.
If you want to use a namespace in a class, you have to declare an
import in class definition.
The import occurs in NameSpaceOfClass that also deals with class variables.
2011/4/16 Mariano Martinez Peck <marianopeck at gmail.com>:
> YEs, what Guille mentions is from GlorpTest from VW. Do you know if in VW
> they still use PoolDictionaries instead of shared pools?
> On Sat, Apr 16, 2011 at 10:14 PM, Stéphane Ducasse
> <stephane.ducasse at inria.fr> wrote:
>> You should use a SharedPool
>> Have a look at what we did for TextConstant.
>> PoolDictionaries are not stored as dictionary in Squeak since ages.
>> On Apr 16, 2011, at 10:06 PM, Guillermo Polito wrote:
>> > Hi!
>> > I have a class who has a pool dictionary defined as
>> > ... subclass: #MyClass
>> > instanceVariableNames: ''
>> > classVariableNames: ''
>> > poolDictionaries: 'MyPoolDict'
>> > ..
>> > And when I load that class from monticello, he warns me with
>> > This package depends on the following classes:
>> > "MyPoolDict"
>> > You must resolve these dependencies before you will be able to load
>> > these definitions:
>> > If before loading the package I declare a global named MyPoolDict it
>> > loads well...
>> > Of course, I can put a preload in a metacello configuration to declare
>> > the global, but it sucks :).
>> > Can anyone point me in the right direction? (or maybe it's a bug... :/)
>> > Thanks!
>> > Guille
More information about the Pharo-project