[Pharo-project] [squeak-dev] Re: Smalltalk at: #Foo - needs clarification
bschwab at anest.ufl.edu
Wed Oct 6 12:43:45 EDT 2010
You raise a good point about helping to improve code, and I would MUCH rather see us try "aClass environment" for a while before introducing name spaces. Dolphin started leaning toward environments a long time ago, and suddenly "class names" were messages to the environment, and I was completely blown away by the potential power of it.
So, I'm very open to the idea. However, I don't see any harm in ( Smalltalk at:#SomethingNotYetInstalled ), which I have had to use extensively in Migrate's image building code. Is there a better way to do the same thing?
From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua at gmail.com]
Sent: Wednesday, October 06, 2010 12:31 PM
To: The general-purpose Squeak developers list
Cc: Pharo Development
Subject: Re: [Pharo-project] [squeak-dev] Re: Smalltalk at: #Foo - needs clarification
On 6 October 2010 19:08, Andreas Raab <andreas.raab at gmx.de> wrote:
> On 10/6/2010 6:58 AM, Igor Stasenko wrote:
>> just wanna ask, is this part of API will be deprecated in future?
>> (in Pharo, it put under 'to clean later' category).
>> And if yes, then what will be correct (dialect-agnostic) way to access
>> Smalltalk globals at: #Foo ?
>> I thought that #at: #at:put: (and some others)
>> historically is a part of Smalltalk protocol, and should stay there to
>> support legacy code and cross-dialect code.
>> What you thoughts about it?
> The base dictionary access methods (#at:, #at:put:, #at:ifAbsent:) should
> remain in Smalltalk for compatibility. Then it's a matter of where that
> request is being delegated.
Yes, i am also thinking that for compatibility it should stay.
Then i think in modern code, a most future-proof way is
self class environment at: #Foo
since it completely avoids any kind of early-binding.
> - Andreas
Igor Stasenko AKA sig.
Pharo-project mailing list
Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev