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

List:       pykde
Subject:    Re: [PyKDE] C++ signature/undefined types
From:       "Phil Thompson" <phil () riverbankcomputing ! co ! uk>
Date:       2005-07-31 16:11:33
Message-ID: 10974.64.110.51.254.1122826293.squirrel () river-bank ! demon ! co ! uk
[Download RAW message or body]

> Given the following sip fragment...
>
> class Foo
> {
>   virtual void bar( SIP_PYOBJECT ) [void (UnwrappedType)];
> %MethodCode
>   // ...
> %End
> %VirtualCatcherCode
>   // ...
> %End
> };
>
> Sip will compain about UnwrappedType not being defined.  I don't
> believe it should need to be defined in the presence of the
> %VirtualCatcherCode, as it is only used verbatim in the method's
> argument list.
>
> I had a look at relaxing this restriction myself, but given my limited
> experience with sip internals, this change seems non-trivial.
>
> Is it possible to relax the type checking for C++ signatures in the
> presence of hand written virtual handler code?

I'll add it to the TODO list, but I won't get around to it soon.

The easiest workaround is to define it as a %MappedType and provide dummy
type convertors.

Phil

_______________________________________________
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]