Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80178
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.169 as permitted sender)
Message-ID: <54AABB2F.3080803@gmail.com>
Date: Mon, 05 Jan 2015 16:26:23 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com> <CAMUwpuRG15LYh27-68=b6CNzo0AhJ5zhTML7ii0AxgjuvY_rBA@mail.gmail.com>
In-Reply-To: <CAMUwpuRG15LYh27-68=b6CNzo0AhJ5zhTML7ii0AxgjuvY_rBA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files
From: rowan.collins@gmail.com (Rowan Collins)

Julien Pauli wrote on 05/01/2015 16:19:
> 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

The RFC explains the motivation reasonably clearly. In particular:

 > Using RINIT is error prone and a little bit dangerous, because is a 
bit too early for some data to be cleanly created (globals).

Basically, it's a standardised implementation, and allows the code to 
run at a more appropriate phase of execution.

-- 
Rowan Collins
[IMSoP]