On Wed, Jul 29, 2009 at 6:06 PM, Andreas Wacknitz <A.Wacknitz@gmx.de> wrote:

Am 29.07.2009 um 20:08 schrieb Marcus Denker:

>
> On 29.07.2009, at 14:02, Andreas Wacknitz wrote:
>
>>
>> Am 29.07.2009 um 17:46 schrieb Damien Cassou:
>>
>>> On Wed, Jul 29, 2009 at 5:20 PM, Andreas Wacknitz<A.Wacknitz@gmx.de>
>>> wrote:
>>>> When I learned object orientation one of the first things I
>>>> encountered was:
>>>> "Procedural code makes decisions, object oriented code delegates."
>>>> Or, sometimes simply: "Tell, don't ask!".
>>>> For me this looks like asking...
>>>
>>> I agree but this would be a good start I think.
>> A start in what direction? Is there a plan to change this later? And
>> if so, when, who and how?
>>
>
> The old Squeak desease was that nothing ever was done, because at some
> point
> it was found that "we could do better". This resulted in *complete*
> paralysis.
>
> For Pharo, the idea is to do something if it�s better. Just imagine
> what you can
> do in 10 years if you do a lot of little things a little bit better.
> Instead of
> doing nothing and waiting for perfection.
>

I understand your point but part of Squeak's problem is its actual
state.
Many things are really messy and crappy.
While the proposed solution might be better for the actual problem (a
special unit test for the Mac),
I really fear a new source for code rot. When this isXXX will be
established it will be used in other situations

Yes. I am agree. The thing is, who will do it?  Ho has the time to understand every place and change it ?
 

sooner or later. And I can't see that
       OSPlatform current isMacOSX
is really that much better than

       SmalltalkImage current platformName = 'Mac OS'

Yes it is. I it is not MUCH better, but a bit better and easy to implement. Tomorrow the platform name changes and you have to change your code all over the image. At least, with this, you have the hardcoded in a single place. After this, with a single "senders" you can see where it is used and how to modify this for a more OO stuff.