Fwd: Delivery Status Notification (Failure)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Fwd: Delivery Status Notification (Failure)

stephane ducasse-2
>
> We should have a MetacelloRepository for Pharo1.0 and Pharo1.1
> and probably metacello should support versions too.
>
> Stef
>
> On Jul 20, 2010, at 5:59 AM, Miguel Enrique Cobá Martínez wrote:
>
>> El sáb, 10-07-2010 a las 12:14 -0300, Germán Arduino escribió:
>>
>>> I saw that exist a preference, but seems not work.
>>>
>>> Also a closed issue talking about this topic (1544) but really don't
>>> understand how to use this in Pharo 1.0.
>>>
>>> Any clarification will be appreciated.
>>
>> Hola Germán,
>>
>> just have the time to check this issue. I found the problem.
>> This configuration was made and tested for PharoCore 1.0 (and maybe
>> Pharo 1.0 but I always test on Pharo Core images). The version I
>> published with support for 1.1r1 was
>>
>> ConfigurationOfMagma-MiguelCoba.31.mcz from 3 June 2010, 7:40:32 pm.
>>
>> Thas was tested, as I said, in PharoCore 1.0. In pharo core 1.0 the
>> underscores are allowed.
>> Also, in PharoCore 1.0 the setting is changed in a preference
>>
>> Preferences class>>allowUnderScoreAssingment.
>>
>> Remember that currently only PharoCore 1.0 is released and stable. 1.1
>> is frozen and 1.2 is unstable.
>>
>> Now, the configuration was modified in order to work for 1.1 and 1.2.
>> So the method:
>>
>> ConfigurationOfMagma>>preLoadForPharo
>> "Magma extends EventSensor that was replaced by InputEventSensor in
>> Pharo and Magma still has underscore code"
>>
>> Smalltalk at: #EventSensor put: InputEventSensor.
>>
>> got this line added:
>>
>> Scanner allowUnderscoreAsAssignment: true.
>>
>> But this is correct only for Pharo 1.1 and 1.2. In those versions of
>> pharo, is the Scanner class the responsible of allowing or not the
>> underscore in the code. In Pharo 1.0 that method doesn't exist in
>> Scanner class. So the error you saw.
>>
>> So the configuration of magma now loads in 1.1 and 1.2 but is broken on
>> the stable release.
>>
>> fortunately this can be reverted and everything will be ok. But...
>>
>> two things:
>>
>> - If we modify a stable configuration in order to make it work in a RC