On 04 Dec 2013, at 20:34, Stéphane Ducasse <stephane.duca...@inria.fr> wrote:
> >>> 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… > > Ok I will check something on UndefinedObject to start with. > Then it would be fun to prototype a kind of strategy hiearchy on the side > (extracted from also) behavior of OCSemanticsError > It was nice to see it and since now I'm ok to have a look at the compiler > code it was interesting. > The current design is motivated mostly by backward compatibility, not anything else. Marcus