Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73224
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 74.125.83.53 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
In-Reply-To: <CAEZPtU4G6tDQtWrbr4-5puSGDA4pdJ914aiBxoXwWvbNJ61Y6g@mail.gmail.com>
Date: Mon, 17 Mar 2014 18:05:45 +0100
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <2330CFB2-B1AD-42F7-ABD2-525E24BA9FC9@googlemail.com>
References: <CAEZPtU4G6tDQtWrbr4-5puSGDA4pdJ914aiBxoXwWvbNJ61Y6g@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Subject: Re: [PHP-DEV] very nice c++ binding for the internals APIs
From: ingwie2000@googlemail.com (Kevin Ingwersen)

The example blew my mind. Why can=92t this be like, integrated into the =
core? XD
If that - c++ api - and an easier way to build php would be present, =
that would be awesome=85but i will be writing an email about the easier =
build at some other day. Basicaly, just to make libphp able ot be easier =
integrated into an existing build system=85 o.o
Am 17.03.2014 um 17:57 schrieb Pierre Joye <pierre.php@gmail.com>:

> hi,
>=20
> http://www.php-cpp.com/ is a very nice c++ API to write PHP
> extensions. I can imagine something like that in the core as well for
> those willing to implement their extensions using c++.
>=20
>=20
> Cheers,