========== 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 SqueakDebug.log (13K) Download Attachment |
Ah, probably a problem with load order. I will check that. 2013/9/21 Bob Arning <[hidden email]>
|
So Monticello-nice.571 is using a message added in Compiler-nice.270 That means that I should have placed Compiler-nice.270 in an intermediate update or higher in the package order...So does Kernel-nice.808 2013/9/21 Nicolas Cellier <[hidden email]>
|
Argh try again! I just republished again. Monticello-nice.571 uses Kernel-nice.808 which uses Compiler-nice.2702013/9/21 Nicolas Cellier <[hidden email]>
|
In reply to this post by Nicolas Cellier
Ran mostly without problem. Got one of those
monticello merge-whatever windows complaining about
TheWorldMenu>>soundEnablingString. I clicked keep and merge
and it went away. Whatever that means.
Cheers, Bob On 9/21/13 5:38 PM, Nicolas Cellier
wrote:
|
It means that we both changed the same method, so there is a merge conflict. Right now, the method for resolving is binary: If you say keep, then you accept the incoming version to replace your version.2013/9/21 Bob Arning <[hidden email]>
|
Nothing really needs to be done - it was the
same change. I needed to make it first to get the help menu in
order to update to your version.
On 9/21/13 6:00 PM, Nicolas Cellier
wrote:
|
If you click on the squeak icon, left of top menu bar, it's also the second item. 2013/9/22 Bob Arning <[hidden email]>
|
Free forum by Nabble | Edit this page |