On Tue, May 5, 2009 at 3:34 PM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi Mariano,

I think the problem is that since #localize is not implemented the
system stops working because it depends on String>>printOn:
(considering that source code is a string too...).

Yes. I think this is the reason.
If you first
implement #localize and then implement #printOn: it seems to work ok.

I tried that and works ok.

In any case, overriding String>>printOn: does not seem to be a good
idea.

Yes. I know. But, there is a reason. I need to get int18 in Pier components because my final user (spanish) will do thing with Pier, like posting, and I need to have it in Spanish. I thought I could override String >> printOn:��� so that translate to spanish. However, I couldn't test this solution. I was going to tested and then send an email to Pier list and see if there is a better solution for this. I don't want to touch Pier code.

Thanks for your concern about that ;)


HTH,
Adrian

On May 5, 2009, at 17:52 , Mariano Martinez Peck wrote:

> Fuck....It seems to be more complex to reproduce. These are the
> steps I am
> doing
>
> 1) open OB.
> 2) go to String class, method �printOn:
> 3) modify printOn: to this:
>
> printOn: aStream
> � �"Print inside string quotes, doubling inbedded quotes."
>
> � �self size < 100
> � � � � ifTrue: [ self localize storeOn: aStream ]
> � � � �ifFalse: [ self storeOn: aStream ]
>
> 4) �save it and put initials if asked.
> 5) as localize is not created yet, it ask you the selector. Ignore
> it and
> select localize �(the first option)
> 6) ctrl + a (select all text) and try to create the method localize.
> It can
> be just empty this method.
> 7) try to save
> 8) your image may be freeze :)
>
>
> Can you confirm this ? I am sorry I said I was on Linux. I thought I
> was at
> home, but �not, unfortunately I am with Windows at work :(
>
> Cheers,
>
> Mariano
>
>
> On Tue, May 5, 2009 at 2:40 PM, Alexandre Bergel
> <alexandre@bergel.eu>wrote:
>
>>> Cool! I'm currently collecting all the cases which freezing an
>>> image,
>>> to find a best way in new scheduler how to prevent that.
>>> I need more!! :)
>>>
>>> :) � �But does this happen also to you ?
>>
>>
>> In a 10300 on OSX I can do without any problem:
>> String compile: 'foo ^ 60'. 'abc' foo
>> => 60
>>
>> Something more you want me to test ?
>>
>> Alexandre
>>
>>
>>
>>>
>>>
>>>> Cheers,
>>>>
>>>> Mariano
>>>>
>>>> _______________________________________________
>>>> Pharo-project mailing list
>>>> Pharo-project@lists.gforge.inria.fr
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Igor Stasenko AKA sig.
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel �http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project