[PyQt] Const-correctness of sipCpp

Phil Thompson phil at riverbankcomputing.co.uk
Fri Dec 4 19:08:42 GMT 2009

On Fri, 04 Dec 2009 12:44:28 +0100, Giovanni Bajo <rasky at develer.com>
> Hi Phil,
> Within %MethodCode, sipCpp is not const-correct: it always is of
> non-const pointer type, even within const methods.
> This can cause some subtle bugs, for instance when accessing a method
> which has two overloads (a const one, and a slower non-const one, as it
> usually happens with containers, for instance).
> I believe it would make sense for sipCpp to be a const pointer type when
> accessed from within the %MethodCode of a const method.

Agreed - added to the TODO list.


More information about the PyQt mailing list