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

List:       pykde
Subject:    Re: [PyQt] Const-correctness of sipCpp
From:       Phil Thompson <phil () riverbankcomputing ! co ! uk>
Date:       2009-12-04 19:08:42
Message-ID: ddc38f6a6382fb98d3107c0f87ec93c4 () localhost
[Download RAW message or body]

On Fri, 04 Dec 2009 12:44:28 +0100, Giovanni Bajo <rasky@develer.com>
wrote:
> 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.

Phil
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]