Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80143
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
MIME-Version: 1.0
Sender: reeze.xia@gmail.com
In-Reply-To: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com>
References: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com>
Date: Sun, 4 Jan 2015 20:33:52 +0800
Message-ID: <CAG1chor6XY1WoozX92g+xshx3Pt+zhTLKZABt-5tjKg-OpNJOQ@mail.gmail.com>
To: Benjamin Eberlei <kontakt@beberlei.de>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d043c08b682e631050bd2cace
Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files
From: reeze@php.net (reeze)

--f46d043c08b682e631050bd2cace
Content-Type: text/plain; charset=ISO-8859-1

I like the idea, I have implemented a util [1] to help writing extensions
with PHP, I try the approach HHVM adopted by embedding PHP scripts to the
binary file of extension, maybe it is what you want.  I do like it been
supported in core. I would like to implement the RFC if others like it.

---
[1] https://github.com/reeze/php-ext-embed


On 4 January 2015 at 19:52, Benjamin Eberlei <kontakt@beberlei.de> wrote:

> Hey everyone,
>
> I want to open discussion on my RFC to strengthen the ability of extensions
> to provide functionality to developers in both C **and** PHP code.
>
> For this extensions can add PHP files to a list of "prepend files" that are
> part of every request execution exactly the same way the INI
> auto_prepend_file functionality works:
>
> https://wiki.php.net/rfc/extension_prepend_files
>
> I propose implementation details in the RFC, but they are completely up to
> discussion. I am even sure there is probably a better way than what I
> proposed, because I am not familiar with the code.
>
> greetings
> Benjamin
>

--f46d043c08b682e631050bd2cace--