Hey Lou

Am 05.03.2013 um 22:18 schrieb Louis LaBrunda <Lou at Keystone-Software.com>:

>>> One could say that about anything you might want to play with in a
>>> workspace.
>> I'm not opposed to workspaces, but when you are spending energy to make 
>> a workspace do what a class & method will already provide, seems like 
>> re-inventing the wheel.
>>> As I said, I often work up code in a workspace and then copy it
>>> to a method when I'm happy with it.  If I can't use pool references in the
>>> workspace, I then have to change things when I want to make a real method.
>> I don't understand this part. If you put it in a method from the start, 
>> then when it works, you're done.
> 
> I often have to play with objects (not so much in Squeak but in my VA
> Smalltalk work) that would cause problems if I instantiated them in order
> to test a new method.  Sometimes I can't even test them on my computer but
> have to test them in production (they want to talk to some host that I
> don't have access to).  If I instantiate them they start doing things I
> don't want them to do and they interfere with the testing.  So, I can and
> must do a lot in a workspace.  It may not be ideal but that's life.


I can relate there ;)

I am curious why you want to use Pool Dictionaries in the first place.
Not that I question them, but I have up until now never hat the necessity
to use them, so I would be delighted to see why they are useful :)

Best
	-Tobias