Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:910
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <20030414165427.66854.qmail@pb1.pair.com>
To: internals@lists.php.net
Reply-To: jay@php.net
Mail-Copies-To: jay@php.net
Date: Mon, 14 Apr 2003 12:54:22 -0400
References: <20030412125758.GA5060@mail.host.sk> <20030414142344.28249.qmail@pb1.pair.com> <1050336627.1114.129.camel@salem.intra.nobolt.net> <20030414162635.38228.qmail@pb1.pair.com> <1050337980.1093.133.camel@salem.intra.nobolt.net>
Lines: 27
User-Agent: KNode/0.7.2
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Subject: Re: [PHP-DEV] Re: Linking problem with extension written in C++
From: jay@php.net (Jay Smith)


I believe Zeev suggested doing it on a per API function basis. Should be in
the archives some place, so I can't take credit for the suggestion. I don't
really care how it's done either, so long as it works. Looking over the
Zend code, it seems that most of the ZEND_API are wrapped in
BEGIN/END_EXTERN_C(), so for the sake of consistency that's probably the
way to go.

J


Per Lundberg wrote:

> On Mon, 2003-04-14 at 18:26, Jay Smith wrote:
>> It kind of seems messy to wrap everything in extern "C".
> 
> Well, I think it's kind of standard procedure when writing C APIs.  Do a
> grep on __cplusplus in your /usr/include for example.  But do it any way
> you like, as long as it works...
> --
> Best regards,
> 
> Per Lundberg / Capio ApS
> Phone: +46-18-4186040
> Fax: +46-18-4186049
> Web: http://www.nobolt.com