Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80274
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.11.1501081140510.4080@whisky.home.derickrethans.nl>
References: <CAEPJdu=2oWiSCQOTkO1g5QDs4NrJwd5H14Jks17qrNu7-eQNVg@mail.gmail.com>
	<CAESVnVqAHJujo0anMi7QYhSZeErcfRVAJ=M7oQMG-huk-bxpCg@mail.gmail.com>
	<54AAF98B.4020709@gmail.com>
	<alpine.DEB.2.11.1501061120440.4080@whisky.home.derickrethans.nl>
	<CAEZPtU69a2MwH5aqigAUEp8+KcjR+w9pd81EvzvM1_z4ES34rQ@mail.gmail.com>
	<001b01d029bb$fa687fc0$ef397f40$@tekwire.net>
	<alpine.DEB.2.11.1501070959000.4080@whisky.home.derickrethans.nl>
	<CAEZPtU67htboPTt6PefLaEREbkobnPY=BpjKpRGg3B1o8xC0Vg@mail.gmail.com>
	<00a201d02ac7$406a4830$c13ed890$@tekwire.net>
	<CAEZPtU5m+U4-PCHzqRBOFweOzuj7VzFLNmRVXDUG8aFjeMcU7A@mail.gmail.com>
	<alpine.DEB.2.11.1501081140510.4080@whisky.home.derickrethans.nl>
Date: Thu, 8 Jan 2015 03:51:13 -0800
Message-ID: <CAEZPtU6Pec3h8exnDQymYqOdGCRtJdXhr-j6ND80_Xd0HGyPDw@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>, 
	PHP internals <internals@lists.php.net>, Sara Golemon <pollita@php.net>, 
	Stanislav Malyshev <smalyshev@gmail.com>, Benjamin Eberlei <kontakt@beberlei.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files
From: pierre.php@gmail.com (Pierre Joye)

On Thu, Jan 8, 2015 at 3:43 AM, Derick Rethans <derick@php.net> wrote:
> On Wed, 7 Jan 2015, Pierre Joye wrote:
>
>> On Wed, Jan 7, 2015 at 2:14 PM, Fran=C3=A7ois Laupretre <francois@tekwir=
e.net> wrote:
>> >> De : Pierre Joye [mailto:pierre.php@gmail.com]
>> >>
>> >> ... here, it is proposed to bundle scripts that will be executed at
>> >> runtime like any other script, except that nothing can be done with
>> >> them, not even disable them if not required (like using its own
>> >> glue codes).
>> >
>> > I agree. Bundling scripts in extensions to execute them at each
>> > RINIT is, IMO, not a good idea (mostly for performance reasons and
>> > lack of control, as you note), but I keep thinking that a mechanism
>> > to embed PHP scripts in extensions and make them available via a
>> > common stream wrapper can be useful. What I don't like is the fact
>> > to execute them automatically at every RINIT. I prefer to let the
>> > extension free to load its PHP code when its logic decides it is
>> > needed.
>>
>> Or let the extension defines a script to prepend, preload, whatever we
>> end to do.
>>
>> It is however important, as you mentioned, to leave the engine and the
>> user the ability not to load it, at all.
>
> No no, *not* loading the code is exactly what I want to prevent people
> from doing! The PHP library code is an *integral* part of the extension.
> Without it, its APIs and functionality would be useless.

Sorry but yes. It is PHP code, and I, for one, want to be able to do
not use it if I do not like it or do not need it.

> pickle, two packages, or any of that other mallargy are not going to fix
> this. It needs to be one package for this to work well, *without* the
> possibility of users messing things up.

Users are not stupid. It is possible to have one package only already. Take=
 #24.

Now I will come back with the patch to provide a solution that users
cannot mess up, as you nicely said and examples. Keeping in mind that
it is already possible to do but not as easy and userfriendly as it
should be (like manual include or the like).

Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org