Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80273
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain beberlei.de from 74.125.82.42 cause and error)
MIME-Version: 1.0
In-Reply-To: <CAEZPtU4kAEHRyggjObUra8yan2PLMw3XYrUuzEV5LfP5eiVxFQ@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>
	<CAEZPtU4kAEHRyggjObUra8yan2PLMw3XYrUuzEV5LfP5eiVxFQ@mail.gmail.com>
Date: Thu, 8 Jan 2015 12:47:53 +0100
Message-ID: <CAEPJdukrQG0ajrNgtU9JCRNpTH_BZbpX9-ztai76FimDP0OvpQ@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
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: multipart/alternative; boundary=f46d043895774866d0050c229c28
Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files
From: kontakt@beberlei.de (Benjamin Eberlei)

--f46d043895774866d0050c229c28
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

You are not forced to use the glue code, its just always available. That is
what an extension is about, always available code. An option would of
course be to not use the extension if you don't need it.

Developers can feel free to use the low level API just like PHP also ships
high and low level stream functions for example.

On Thu, Jan 8, 2015 at 12:43 PM, Pierre Joye <pierre.php@gmail.com> wrote:

> hi,
>
> On Thu, Jan 8, 2015 at 3:41 AM, Benjamin Eberlei <kontakt@beberlei.de>
> wrote:
> >
> >
> > On Wed, Jan 7, 2015 at 11:14 PM, Fran=C3=A7ois Laupretre <
> francois@tekwire.net>
> > wrote:
> >>
> >> > De : Pierre Joye [mailto:pierre.php@gmail.com]
> >> >
> >> > ... here,
> >> > it is proposed to bundle scripts that will be executed at runtime li=
ke
> >> > 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 i=
n
> >> 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 it=
s
> >> logic decides it is needed.
> >
> >
> > To be honest, I don't see the use case of shipping optional PHP code
> inside
> > an extension. As the user of an extension I want all the
> functions/classes
> > to be available all the time, no matter if the extension developer wrot=
e
> > everything in C or in PHP.
> >
> > For optional code there is Composer/PEAR/php include path, this is
> already 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,
> --
> Pierre
>
> @pierrejoye | http://www.libgd.org
>

--f46d043895774866d0050c229c28--