Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80177
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.47 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com>
References: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com>
Date: Mon, 5 Jan 2015 17:19:59 +0100
Message-ID: <CAMUwpuRG15LYh27-68=b6CNzo0AhJ5zhTML7ii0AxgjuvY_rBA@mail.gmail.com>
To: Benjamin Eberlei <kontakt@beberlei.de>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec53d526f3dd964050bea12f9
Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files
From: jpauli@php.net (Julien Pauli)

--bcaec53d526f3dd964050bea12f9
Content-Type: text/plain; charset=UTF-8

On Sun, Jan 4, 2015 at 12:52 PM, 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.
>

Hello.

Can't this be already done somehow ? In RINIT stage obviously.
I don't understand why to change our API to add a feature we already can
use ?

Julien.P

--bcaec53d526f3dd964050bea12f9--