[cairo] Extending Cairo API to support reusable paths

Benjamin Otte otte at redhat.com
Tue Apr 20 03:50:45 PDT 2010

On Tue, 2010-04-20 at 07:14 +0300, M Joonas Pihlaja wrote:
> This gives me pimples.  The returned pointer type ought to be typed, 
> so that the responsibility of keeping track of types is with the 
> implementor rather than the user of these APIs.  It's okay to be a 
> completely opaque type imho, but not one that says "whatevah, I do 
> what I want!" one.
I just assumed that the retained path is a cairo object with a type and
backend pointer like all surfaces and devices and having the same
reference/destroy/finish/set_user_data methods like all other cairo
objects do.

So I was thinking that's just the backend functions. Was I wrong?


More information about the cairo mailing list