[squeak-dev] Importing "namespace" dictionary's vs. Importing Environments

Chris Muller asqueaker at gmail.com
Mon Dec 23 22:55:36 UTC 2013


I hope we can reset from the other thread and work productively
through another question I have about Environments.

Take a look at references to inst-var Environment>>'public', and see
if you can identify how anything ever gets into that Dictionary.

When I look to EnvironmentTest>>#testExplicitExport -- I see the
intent is for me to access the internal Dictionary directly from the
outside and do some #at:put:'s on it.

So, unless I have EnvironmentsTests loaded, Environments by itself
does not "reveal" enough about its API for me to understand how I'm
supposed to use it.

Whenever I have something that's wrapping a Collection, I typically
like to make access to the internal collection private and provide
API's on the wrapping object so everything is tight, controlled and
also obvious.

So I'm wondering whether it wouldn't be tighter to import entire
_Environments_ rather than only their 'public' Dictionary "namespace".

Pile on everybody!    :)


More information about the Squeak-dev mailing list