[cairo] API completeness of reference/user_data pairs

Behdad Esfahbod behdad at behdad.org
Mon Feb 5 08:06:01 PST 2007

On Mon, 2007-02-05 at 09:46 +0800, Steve Chaplin wrote:
> The cairo manual section "Creating a language binding / Memory
> Management",
> says (regarding the problem of subclassing) "This is not easily
> fixable
> without creating memory leaks, and it's probably best to simply forbid
> deriving from the language objects." - and that's what pycairo does
> (with the
> exception of cairo.Context).

So, anyone knows about the roots of that sentence?  Is it just from
before the user-data APIs landing in?  Carl?

> It can be misleading comparing GTK+/PyGTK with cairo/pycairo. GTK+ is
> deliberately written to be object-oriented (requiring GObject) and
> cairo
> is not object-oriented, and does not require GObject.

I know, and I mentioned that already.


"Those who would give up Essential Liberty to purchase a little
 Temporary Safety, deserve neither Liberty nor Safety."
        -- Benjamin Franklin, 1759

More information about the cairo mailing list