Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:4513
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <034401c37d2d$26eccf80$0702a8c0@TITAN>
To: <internals@lists.php.net>, "Igal Ore" <iore@cipherquest.com>
Cc: <jay@php.net>
References: <20030917141743.65402.qmail@pb1.pair.com> <20030917142722.84139.qmail@pb1.pair.com> <033101c37d2a$b6bbdf50$0702a8c0@TITAN> <3F687746.8010208@cipherquest.com>
Date: Wed, 17 Sep 2003 16:05:37 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: C++ extension question
From: wez@thebrainroom.com ("Wez Furlong")

No, that only prevents the file being included twice in the same .cpp file.
The solution to this problem is to move the function bodies into their own
.cpp file:

foo.h:
class Foo {
Foo();
~Foo();
};

fooclass.cpp:
Foo::Foo() { ... }
Foo::~Foo() { ... }

--Wez.


----- Original Message ----- 
From: "Igal Ore" <iore@cipherquest.com>
To: <internals@lists.php.net>; "Wez Furlong" <wez@thebrainroom.com>
Cc: <jay@php.net>; <internals@lists.php.net>
Sent: Wednesday, September 17, 2003 4:01 PM
Subject: Re: [PHP-DEV] Re: C++ extension question


> you are right , and for those cases there a preprocessor protection
> #ifndef DO_NOT_MAKE_BOBO
> #define DO_NOT_MAKE_BOBO
>
> class Foo{
> Foo(){...}
> ~Foo(){...}
> };
> #endif
>
>
> isn't it?
>
> Wez Furlong wrote:
> > This sounds like the "rookie" mistake of declaring your functions inline
in
> > the class definition in the header files, and then including those
headers
> > in multiple files.
> >
> > eg: foo.h:
> >
> > class Foo {
> >   Foo() { ... }
> >   ~Foo() { ... }
> > };
> >
> > foo.cpp:
> > #include "foo.h"
> >
> > bar.cpp:
> > #include "foo.h"
> >
> > == linker problems.
> >
> > --Wez.