) { ... }
--Wez.
- Original Message -
From: "Igal Ore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Wez Furlong" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 4:01 PM
Subject: Re: [PHP-DEV] Re: C++
: "Igal Ore" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; "Wez Furlong" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 4:01 PM
Subject: Re: [PHP-DEV] Re: C++ extension question
> you
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 defin
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 pro
I'm assuming "delete" isn't a function but the C++ operator delete. You're
probably #including the same file more than once, but I doubt it's in Zend.
If all else fails, you can try passing "/FORCE" to the linker options and
it'll try to force the linkage. It might result in a broken binary, tho
