On 04 Dec 2013, at 20:02, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
AnUnknownClass subclass: #Adaptor1Example instanceVariableNames: 'customers accountID address name phoneNumber' classVariableNames: '' poolDictionaries: '' category: 'Examples-Cookbook'
executes the default action for OCUndeclaredVariableWarning, which is opening a pop-up titled: "Unknown variable ...". Here the error is raised at compilation time, therefore it would have no effect to wrap this with a #on:do:
I to me CompilerException should have nothing to do with UI and popup. Then we should be able to pass objects that knows how to handle the errors in interactive way or not.
As a clear example, this is just bad that each time we want to change the UI message we have to change the compiler exception. ugly at wish.
I have no cycle to fix that now. I will check if I can get something in UndefinedObject so that I can continue to work on my task.
The whole exception / error handling of the compiler needs to be deeply rethought. Sadly I have no cycles free in my brain to even start to think about it, and, even more important, we should wait until the old Compiler is removed⦠Marcus