>> 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.
I see :) I would really to see an headless, interactive and scriptable scenarios to be exercised. So this is good it will get better :) Stef
