[cairo] API Shakeup: Consistent error handling for all objects

[Kent Sandvik]

On Wed, 23 Feb 2005 16:56:28 -0500, Carl Worth <cworth at cworth.org> wrote:
> I propose making all objects in cairo use an error handling scheme
> similar to cairo_t. That is, rather than each function returning
> cairo_status_t, most functions are void and error state is stored in
> the object itself, (and can be queried). An object in an error state
> is inert, and functions can be safely called on it with no side
> effects.

I like this approach. Just two quick questions, in case the code is
threaded, will it cause problems if two threads have a different view
of the error state? Also, could the application code clear the error
state, causing problems later? --Kent

-- 
Something, Anything!