Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80271
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEPJdu=ASPf97sWP8RNQzMvCOB3gx2e0SRctGG9wYzkOW2YYew@mail.gmail.com>
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>
	<CAEPJdu=ASPf97sWP8RNQzMvCOB3gx2e0SRctGG9wYzkOW2YYew@mail.gmail.com>
Date: Thu, 8 Jan 2015 03:43:26 -0800
Message-ID: <CAEZPtU4kAEHRyggjObUra8yan2PLMw3XYrUuzEV5LfP5eiVxFQ@mail.gmail.com>
To: Benjamin Eberlei <kontakt@beberlei.de>
Cc: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>, 
	Derick Rethans <derick@php.net>, PHP internals <internals@lists.php.net>, Sara Golemon <pollita@php.net>, 
	Stanislav Malyshev <smalyshev@gmail.com>
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)

hi,

On Thu, Jan 8, 2015 at 3:41 AM, Benjamin Eberlei <kontakt@beberlei.de> wrot=
e:
>
>
> On Wed, Jan 7, 2015 at 11: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 e=
very
>> RINIT. I prefer to let the extension free to load its PHP code when its
>> logic decides it is needed.
>
>
> To be honest, I don't see the use case of shipping optional PHP code insi=
de
> an extension. As the user of an extension I want all the functions/classe=
s
> to be available all the time, no matter if the extension developer wrote
> everything in C or in PHP.
>
> For optional code there is Composer/PEAR/php include path, this is alread=
y a
> solved problem.

So you are saying that people should be forced to use your glue code
instead of implementing their own when it fits better? I can only
disagree. But even then, it does not make the bundling of php code in
binaries a smart idea.


Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org