Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72586
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <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>
	<60CCD000-56E9-400D-A1AF-029E45B4338B@googlemail.com>
Date: Fri, 14 Feb 2014 10:54:00 +0100
Message-ID: <CAF+90c_kZ5+TayriA37Jt_evBkjTdMEYBAChqRXes909BBsRPA@mail.gmail.com>
To: Kevin Ingwersen <ingwie2000@googlemail.com>
Cc: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>, 
	internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c306f00d006104f25ac9f4
Subject: Re: [PHP-DEV] When will the extension and embedding APIs ever be
 cleaned or documented?
From: nikita.ppv@gmail.com (Nikita Popov)

--001a11c306f00d006104f25ac9f4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 14, 2014 at 1:17 AM, Kevin Ingwersen
<ingwie2000@googlemail.com>wrote:

> Am Fr. Feb. 14 2014 00:04:01 schrieb Johannes Schl=FCter:
> > Mind: "Compatibility is a feature." (Bjarne Stroustrup) The fact that 1=
0
> > 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 tha=
t
> > 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, o=
r
> older, API?
>
> BTW, in the API "book", 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.
>

This is covered in
http://www.phpinternalsbook.com/classes_objects/custom_object_storage.htmla=
nd
http://www.phpinternalsbook.com/classes_objects/custom_object_storage.html#=
overriding-create-objectin
particular :) In the code sample there you'd replace "long
additional_property" with "MyClass *my_class" (and add a delete call in the
free_storage handler and a new call in create_object).

Nikita

--001a11c306f00d006104f25ac9f4--