This is a good change, and I doubt many were using the exception handling aspect anyhow.
Now that that's done and widgets are in a comfortable spot, I'd like to avoid any more large or breaking changes. If someone's got something they're itching to commit, it's time to make a branch. Kevin On 2/11/06, Simon Belak <[EMAIL PROTECTED]> wrote: > > I like keeping everyone on their toes, so here goes another one. ;) > > I have somewhat split error handling functionality into two parts, > validation errors and exceptions. > > *From now on error_handler and tg_errors refer only to validation errors.* > exception_handler and tg_exceptions are introduced to combat exceptions. > > All using generic function dispatch_error directly, take note, signature > has changed. > > If you have any suggestions or gripes, do tell. I would like to finalise > this part of API as soon as possible, allowing some decent documentation > to be had. However having error handling interfere with work-flow or > even (program) design is unacceptable to me. I have no problems with > tweaking or even doing a complete rewrite if need be. > > > Cheers, > Simon > > -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
