qvx wrote:
I guess that I have nothing against ticket #258. However, to automagically call the same function twice (in hope that the next time it will fare better) seems like "overdesign".
It's called twice under the assumption, or hope if you prefer, that the error will be handled in some manner. Strictly speaking re-calling is just a consequence of specialisation rules, preferred way is having an explicitly defined error handler. Indeed, this my be an over-design when faced with an error handling scheme of "let-the-app-crash". :)
On the other hand, I suppose you may have a point. Would it be better to require explicit declaration in form of parameter tg_errors before a method is deemed an error handler (for itself)? If we go this route, how should failed validation be handled than?
Simon
