So Monticello-nice.571 is using a message added in Compiler-nice.270
So does Kernel-nice.808
That means that I should have placed Compiler-nice.270 in an intermediate
update or higher in the package order...
I just republished update-nice.246.mcm with Compiler raised two places
abaove (above Monticello and Kernel).
Could you retry?


2013/9/21 Nicolas Cellier <nicolas.cellier.aka.nice at gmail.com>

> Ah, probably a problem with load order.
> I will check that.
>
>
> 2013/9/21 Bob Arning <arning315 at comcast.net>
>
>>
>> ========== Graphics-tpr.225 ==========
>>
>> An attempt to improve the comment for BitBlt; it was very out of date (no
>> Patterns or MAskedForms in image now) and more than a bit confusing in
>> places. Hopefully this is less so.
>>
>> ========== Monticello-nice.571 ==========
>>
>> Don't pass a category to a Compiler, classifying is not its job.
>>
>> >>> Monticello-nice.570 <<<
>> Now that the SyntaxError restarts the existing Compiler process rather
>> than substitute to it, it is possible to edit method with incorrect syntax
>> in the SyntaxError and continue MC Loading/Merging.
>>
>> Though, we should log the corrected code, not the syntaxically incorrect
>> one, and for that we let MethodAddition intercept the
>> SyntaxErrorNotification so as to retrieve its corrected newSource.
>>
>> ========== Kernel-nice.808 ==========
>>
>> Don't pass a category to a Compiler, classifying is not its job.
>>
>> >>> Kernel-nice.807 <<<
>> If you just need the parameter names, then just ask for the parameter
>> names.
>> Asking for parameter and temp names, then throwing the temps away sounds
>> like not using the right API in the right place...
>>
>> ========== Graphics-tpr.225 ==========
>>
>> An attempt to improve the comment for BitBlt; it was very out of date (no
>> Patterns or MAskedForms in image now) and more than a bit confusing in
>> places. Hopefully this is less so.
>>
>> ========== Monticello-nice.571 ==========
>>
>> Don't pass a category to a Compiler, classifying is not its job.
>>
>> >>> Monticello-nice.570 <<<
>> Now that the SyntaxError restarts the existing Compiler process rather
>> than substitute to it, it is possible to edit method with incorrect syntax
>> in the SyntaxError and continue MC Loading/Merging.
>>
>> Though, we should log the corrected code, not the syntaxically incorrect
>> one, and for that we let MethodAddition intercept the
>> SyntaxErrorNotification so as to retrieve its corrected newSource.
>>
>> ========== Kernel-nice.808 ==========
>>
>> Don't pass a category to a Compiler, classifying is not its job.
>>
>> >>> Kernel-nice.807 <<<
>> If you just need the parameter names, then just ask for the parameter
>> names.
>> Asking for parameter and temp names, then throwing the temps away sounds
>> like not using the right API in the right place...
>>
>> ......then a walkback (attached)..........
>>
>> Cheers,
>> Bob
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20130921/5a1a0e8b/attachment.htm