Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72572
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.215.181 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
In-Reply-To: <1392332641.3990.109.camel@guybrush>
Date: Fri, 14 Feb 2014 01:17:44 +0100
Cc: Nikita Popov <nikita.ppv@gmail.com>,
 internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <60CCD000-56E9-400D-A1AF-029E45B4338B@googlemail.com>
References: <D98B1E8F-933B-4310-8C1B-5202F8BE9996@googlemail.com> <CAF+90c_jPfV+U1dEDT3oOkjuENpse6kqqVCjh6T9XYyzLwtAxA@mail.gmail.com> <1392332641.3990.109.camel@guybrush>
To: =?windows-1252?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>
Subject: Re: [PHP-DEV] When will the extension and embedding APIs ever be cleaned or documented?
From: ingwie2000@googlemail.com (Kevin Ingwersen)

Am Fr. Feb. 14 2014 00:04:01 schrieb Johannes Schl=FCter:
> Mind: "Compatibility is a feature." (Bjarne Stroustrup) The fact that =
10
> years old extensions can be used with php git master with quite little
> work is not only a help for old users but also promise to new users =
that
> their investment won't be lost easily.

But what if there was something like a wrapper above the old api, to =
give it a cleaner appearance, so people could choose to work with the =
newer, or older, API?

BTW, in the API =84book=93, I dont find what I am looking for; storing a =
forgein thing into the object. Like if I was to write a PHP module that =
exports a PHP class, I would like to create a class instance to a C++ =
class, and store that instance within the php object (struct?). Like:

	zval* this =3D getThis();
	MyClass* mc =3D (MyClass*)get_pointer_from_zvalthis);

And, well, vice-versa.

Otherwise, that phpinternalsbook is very detailed, and I like how its =
written :)

Although its no real PHP project - why not just link it in the php.net =
docs? o.o=