[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    [PyKDE] Abstract annotation and deleting objects
From:       James Emerton <james () emdata ! net>
Date:       2005-03-24 1:07:56
Message-ID: 9760bea2b6dc647d316f0f33d7b253e0 () emdata ! net
[Download RAW message or body]

If a sip specification marks a class with the 'Abstract' annotation, 
the CLASS_CANNOT_CREATE bit is set.  This can also be caused by the 
inclusion of pure virtual methods.

The effect of the CLASS_CANNOT_CREATE bit is to set td_init AND 
td_dealloc to 0 in the generated sipTypeDef.  This causes factory 
methods returning pointers to abstract interfaces to leak memory.

I am going to attempt to patch this, but I still don't know the SIP 
code very well at all.  Anyone know any reason why always generating 
the dealloc_CLASS function might be a bad idea?

James

--
This is not my home; the cats just let me stay here.

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]