Re: [PATCH] New changes to ext_skel for C++
| From: | Zeev Suraski | Date: | Mon, 02 Dec 2002 16:16:16 +0000 |
| Subject: | Re: [PATCH] New changes to ext_skel for C++ | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-92014@lists.php.net to get a copy of this message | ||
Why do we need an extern c before php.h? The relevant API functions in php.h should be extern "c"d in my opinion, wrapping php.h up in extern "c" is not very clean.
Zeev
At 17:32 02/12/2002, J Smith wrote:
For the second instance where extern "C" is used, that would be possible, but in the first instance, BEGIN/END_EXTERN_C() aren't defined yet, as they're in zend.h. The compiler would totally barf. I had used BEGIN/END_EXTERN_C() in the first patch I sent out, but decided to use one or the other in this one for the sake of consistency. J Zeev Suraski wrote: Why not just use BEGIN_EXTERN_C() and END_EXTERN_C()? Zeev -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php