Apparently

Parser>>
removeUnusedTemps
     "Scan for unused temp names, and prompt the user about the  
prospect of removing each one found"

     | str end start madeChanges |
     madeChanges _ false.
     str _ requestor text string.
     ((tempsMark between: 1 and: str size)
         and: [(str at: tempsMark) = $|]) ifFalse: [^ self].
     encoder unusedTempNames do:
         [:temp |
         ((UIManager default
                 chooseFrom: #('yes' 'no')
                 title: ((temp , ' appears to be\unused in this  
method.\OK to remove it?')
                         withCRs asText makeBoldFrom: 1 to: temp  
size)) = 1)
         ifTrue:
         [(encoder encodeVariable: temp) isUndefTemp
             ifTrue:
             [end _ tempsMark.
             ["Beginning at right temp marker..."
             start _ end - temp size + 1.
             end < temp size or: [temp = (str copyFrom: start to: end)
                     and: [(str at: start-1) isAlphaNumeric not &  
(str at: end+1) isAlphaNumeric not]]]
             whileFalse:
                 ["Search left for the unused temp"
                 end _ requestor nextTokenFrom: end direction: -1].
             end < temp size ifFalse:
                 [(str at: start-1) = $  ifTrue: [start _ start-1].
                 requestor correctFrom: start to: end with: ''.
                 str _ str copyReplaceFrom: start to: end with: ''.
                 madeChanges _ true.
                 tempsMark _ tempsMark - (end-start+1)]]
             ifFalse:
             [self inform:
'You''ll first have to remove the
statement where it''s stored into']]].
     madeChanges ifTrue: [ParserRemovedUnusedTemps signal]


does not work anymore since when requestor is a SyntaxError,  
requestor does not know how to answer text...


load
     self actualClass
         compile: source
         classified: category
         withStamp: timeStamp
         notifying: (SyntaxError new category: category)

I do not have the time to look into that now.
But this is a first problem.


Then I get often errors related to MouveEventPlus....

Stef




On 5 nov. 05, at 12:54, stéphane ducasse wrote:

> this is long but I cannot do better now...
> Steadily improving is a good idea.
> Imagine how many times I'm building these images....
>
>
> Stef
>
> On 5 nov. 05, at 12:36, Lic. Edgar J. De Cleene wrote:
>
>
>> stéphane ducasse puso en su mail :
>>
>>
>>
>>> But it should reasonably work :)
>>> Please test it.
>>>
>>> Stef
>>>
>>>
>>>
>>>>
>>>>
>>>>
>>>>> This was a bit painful so it really needs to be tested. Thanks  
>>>>> Cees
>>>>> for the help it was good to work on evening together.
>>>>>
>>>>>
>>>>>
>>>>>
>>>> Thanks, the pleasure was all mine :)
>>>>
>>>> People: THIS IS ALPHA!!!!
>>>>
>>>> It will eat your hard drive, kidnap Santa Claus, change the US
>>>> Constitution so that GWB can have an other term, and then will  
>>>> go off
>>>> to do some *really* nasty things.
>>>>
>>>> It needs testing, testing, testing, and bugfixing. We've been  
>>>> juggling
>>>> an awful amount of changesets, and frankly fighting some MC warts
>>>> (like the absence of shadow compilation, hint, hint ;-)), so I do
>>>> expect things to go wrong. Bear with us, take a deep breath, and  
>>>> send
>>>> patches instead of complaints.
>>>>
>>>> Thanks for your cooperation, back to our regular scheduled  
>>>> programme.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>> Well, I have a forever loading update again.
>>
>> Here in South is Spring and  this season have me optimistic.
>>
>> Maybe the trick is abort the loading and try again the next day  
>> (work the
>> last two times ) :=)
>>
>> Edgar
>>
>>
>>
>>
>>
>>
>>
>> ___________________________________________________________
>> 1GB gratis, Antivirus y Antispam
>> Correo Yahoo!, el mejor correo web del mundo
>> http://correo.yahoo.com.ar
>>
>>
>>
>>
>>
>
>
>
>