Re: When will the extension and embedding APIs ever be cleaned or documented?
On Thu, Feb 13, 2014 at 9:22 PM, Kevin Ingwersen
<ingwie2000@googlemail.com>wrote:
> Hey.
>
> Just a while ago, i started writing a C++ library, that I would like to
> utilize in PHP. Since the original aproach was made in C++, I would like to
> keep the OOP syntax in PHP.
>
> Already, months ago, I had tried to find ways to write useful PHP modules.
> But the major problem was always: How. I easily found documentation about
> adding functions...and how to expose a void pointer in the form of a
> "Resource". But that was all that was ever properly documented. The OO
> module api was never really documented, and yet, is still hard to figure
> out. I was sent a slideshow of the api...but is a set of slides a really well
> made documentation? I think not.
>
> Many of you internals probably know the APIs needed to do these things:
>
> - Create a class with public/private/protected methods - thus
> making a class final.
> - Being able to store a pointer to forgein objects into the class,
> to re-use it.
>
I think we have a pretty good coverage of object and class APIs here:
http://www.phpinternalsbook.com :)
> I have been learning to use the v8 API a lot and it has a very clean
> syntax. A third-party scripting language brought it even so far, that it
> could almost map native types to script types - but that was pure C++ -
> both of them.
>
V8 has the benefit of being written in C++ and being a lot newer. HHVM has
really nice extension APIs, all courtesy to C++. But a number of core devs
are rather opposed to using a more powerful language as the basis for PHP
;) *Glares at Pierre*
Nikita
Thread (8 messages)