Returning "Native" PHP Objects from an Extension

Question

I'm dabbling with creating a PHP extension for a personal project. Beyond what's linked in the above article I have no knowledge of the zend_engine, and my C skills are 10 years out of date, and were only ever academic. All of which is to say "If it seems like I'm asking a dumb question, I probably am".

Is it possible to call functions from other PHP extensions in my own extension, or is each PHP extension considered an island, with no insight into other parts of the system? If this is possible, is it common practice, or a Bad Idea™?

That is, I know I can return a string with something like this.

PHP_FUNCTION(hello_world)
{
    char *str;
    str = estrdup("Hello World");
    RETURN_STRING(str, 0);
}

I'd like to be able to return, say, a SimpleXML element, or a DomDocument element. Googling has proven difficult, as there's not a ton out there about extension development, and there IS a ton out there about standard PHP usage.

Redness

Nice question; I'd be surprised though if the Zend documentation didn't shed any light on this. – Lazo

@KerrekSB And that's a nice RTFM :). If you (or anyone) knows of a zend document that has a good overview of this and doesn't assume 5+ years of extension hacking experience (or even one that does) I'd love to see it. – Redness

Answer 1

Yes, extensions can in fact depend on others. They can:

• Use resources that other extensions register globally, such as class types or PHP functions (that is, they don't have less access than user-land scripts, which can obviously use those resources). See zend_call_function and zend_lookup_class_ex.
• Use any exported symbols and structures that are declared in the file php_extensionname.h (these headers are the only ones that are considered to a export a native API to other extensions). However, some extensions may in fact NOT export some symbols declared in those header files, you must look for symbols declared with PHPAPI. Note that some extensions cannot be deactivated and you can rely on them being present (for instance, as of 5.3/5.4, standard, SPL, reflection, date, pcre, ereg).
• If both your extension and target extension are built statically, you have of course more latitude on the symbols you can use, but it's not a good practice to use non-exported symbols.

I'd like to be able to return, say, a SimpleXML element, or a DomDocument element.

If you need to explicitly instantiate a SimpleXMLElement or a DOMDocument, you can do so with object_init_ex. Extensions usually export the zend_class_entry * that have to pass that macro, but if not you can always use zend_lookup_class_ex. This does NOT call the constructor, so you still must do so manually if you need to.

Some extensions may provide a native interface to instantiate and initialize an object, but in general extensions are not prepared to have other extensions instantiate their types.

Of course, you can also, like a script, call PHP functions and methods that return any of those types. You'll get a zval * that you can in turn return from your function.

As to how to declare the dependencies, the extension descriptor has an entry for this. This will ensure your extension is loaded after the ones you declare you depend on. For declaring the dependency at compile time see PHP_ADD_EXTENSION_DEP.

Coaptation

Answer 2

If you're writing extensions, then Extending and Embedding PHP (aka "Sara's Book") is essential reading. It's a bit dated now, but the best resource you'll find available online or off.

Taffrail

Answer 3

i don't know much about php extension writing but you can try this, if you haven't read it yet http://devzone.zend.com/446/extension-writing-part-iii-resources/

using this you can pass any type of resource to php extension

Bistro