[cairo] Making it easier to track down errors
cworth at cworth.org
Mon Jun 20 10:11:53 PDT 2005
On Mon, 20 Jun 2005 09:46:04 +0200, Mathieu Lacage wrote:
> As far as I am concerned, I don't really see the use of a per-cairo-t
> error notification callback (but it does not bother me either) and I
> think a process-wide notification callback for debugging should be more
> than enough for the few rare times you need it.
I'm suitably convinced that adding the per-cairo_t error notify
callback was a bad idea. So I've now removed cairo_set_error_notify
I'll likely make a new cairo snapshot soon and I definitely don't want
any questionable API additions in it.
On Fri, 17 Jun 2005 14:41:20 -0400, Owen Taylor wrote:
> I'd really like to understand what the use cases is for this function...
> why it's being added. It doesn't seem to really address the question
> of making it easy to track down programming errors.
Yes, let's get back on topic and talk about what currently makes it
hard to track down programming errors and what cairo could do to make
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/cairo/attachments/20050620/7285f455/attachment.pgp
More information about the cairo