Re: [PATCH] New changes to ext_skel for C++
| From: | J Smith | Date: | Wed, 04 Dec 2002 15:16:42 +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-92070@lists.php.net to get a copy of this message | ||
As others have pointed out, it is, but I think it would be better to simply
have the code there in the generated C++ source and not at all in the C
source. It would lead to less confusion imho.
I guess it should kind of be assumed that if someone is going the distance
to actually create an extension to PHP, they're probably going to know what
__cplusplus, extern "C" and all that stuff means, but on the other hand,
I've seen (and received) some pretty ridiculous questions on that sort of
stuff dealing with PHP extensions directly.
J
Stig S. Bakken wrote:
> Isn't __cplusplus defined for all C++ compilers?
>
> #ifdef __cplusplus
> extern "C" {
> #endif
>
> #ifdef __cplusplus
> }
> #endif
>
> This is pretty common in library header files at least.
>
> - Stig
>