Re: Re: C++ extension question
| From: | Igal Ore | Date: | Wed, 17 Sep 2003 15:01:26 +0000 |
| Subject: | Re: Re: C++ extension question | ||
| References: | 1 2 3 | Groups: | php.internals php.internals |
| Request: | Send a blank email to internals+get-4512@lists.php.net to get a copy of this message | ||
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.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 inZend.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,though.Igal Ore wrote:I'm receiving this php_TPKCS12.obj : LNK2005 error: _delete already defined in cert.obj php_TPKCS12.obj : warning LNK4006: _delete already defined in cert.obj; second definition ignored