[squeak-dev] Re: Smalltalk vs SmalltalkImage current woes

Juan Vuletich juan at jvuletich.org
Fri Jul 24 17:07:20 UTC 2009


Andreas Raab wrote:
> Igor Stasenko wrote:
>> I am currently using the Cuis, which doesn't having a 'SmalltalkImage
>> current' refactoring..
>
> Ah, one of my favorite rant subjects. First, it's not a refactoring; 
> refactorings leave the public interfaces intact (I really hate it when 
> people call random rewrites "refactoring" code). Secondly I'm still 
> 100% behind what I wrote here about Smalltalk vs. "SamlltalkImage 
> current":
>
> http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-June/118175.html 
>
>
> I'm very glad to hear that Cuis doesn't use SmalltalkImage.

I totally agree with Andreas.

>> Now, Smalltalk == SmalltalkImage current and everyone is happy:
>>  - dictionary lives in separate ivar,
>>  - fat & boring housekeeping stuff lives in SmalltalkImage instance.
>>
>> What you think?
>
> I think it's a definitive improvement to the current situation.

The compatibility trick I suggest for Cuis is really easy. Just add 
SmalltalkImage as a new, empty class, with just one class method 
'current ^Smalltalk'. Simple, clean, and compatible with both original 
and 'SmalltalkImage current' idiom.

>
> Cheers,
>   - Andreas

Cheers,
Juan Vuletich



More information about the Squeak-dev mailing list