--===============1009902226==
Content-Type: multipart/alternative; boundary="Boundary-00=_6fofIs/4NQI4oNg"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--Boundary-00=_6fofIs/4NQI4oNg
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 7bit
On Wednesday 16 July 2008 16:12, Erick Tryzelaar wrote:
> I've got a simple sip file that has:
>
> struct Foo {
> %TypeHeaderCode
> #include "foo.h"
> %End
>
> virtual Foo();
> };
>
> struct Bar: Foo {
> %TypeHeaderCode
> #include "foo.h"
> %End
>
> virtual Bar();
> };
>
>
> That should be valid code though, right?
It's valid C++, sip may or may not accept it (sip only covers a meaningful subset of C++), and it's identical to the following code which sip will accept:
class Foo {
%TypeHeaderCode
#include "foo.h"
%End
public:
virtual Foo();
};
class Bar: Foo {
%TypeHeaderCode
#include "foo.h"
%End
public:
virtual Bar();
};
Jim
--Boundary-00=_6fofIs/4NQI4oNg
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: 7bit
On Wednesday 16 July 2008 16:12, Erick Tryzelaar wrote:
> I've got a simple sip file that has:
>
> struct Foo {
> %TypeHeaderCode
> #include "foo.h"
> %End
>
> virtual Foo();
> };
>
> struct Bar: Foo {
> %TypeHeaderCode
> #include "foo.h"
> %End
>
> virtual Bar();
> };
>
>
> That should be valid code though, right?
It's valid C++, sip may or may not accept it (sip only covers a meaningful subset of C++), and it's identical to the following code which sip will accept:
class Foo {
%TypeHeaderCode
#include "foo.h"
%End
public:
virtual Foo();
};
class Bar: Foo {
%TypeHeaderCode
#include "foo.h"
%End
public:
virtual Bar();
};
Jim
--Boundary-00=_6fofIs/4NQI4oNg--
--===============1009902226==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
PyQt mailing list PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
--===============1009902226==--