Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80296
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <007901d02bb4$f9ccca80$ed665f80$@tekwire.net>
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>
	<31A3F47C-0C5B-46E0-8B34-2105F467FDB3@fredemmott.co.uk>
	<CAEZPtU7=EytMVfA22g-2AYT514s13VJdZ330niyo6rRiwHjFhg@mail.gmail.com>
	<007901d02bb4$f9ccca80$ed665f80$@tekwire.net>
Date: Thu, 8 Jan 2015 18:58:32 -0800
Message-ID: <CAEZPtU5qOjrygOK0_Jpoub4u1CpHibEd+57YPAfJyZ=bOiniUg@mail.gmail.com>
To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@tekwire.net>
Cc: Fred Emmott <fred@fredemmott.co.uk>, Derick Rethans <derick@php.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 6:35 PM, Fran=C3=A7ois Laupretre <francois@tekwire.n=
et> wrote:
>> De : Pierre Joye [mailto:pierre.php@gmail.com]
>>
>> > We solved some of the other problems by only allowing definitions, no
>> side-effects - classes, constants, namespaces etc. We do not allow code
>> outside of a function body here.
>>
>> Yes, we will have to do that, no matter what we choose. I am however
>> not sure how to do it with the current engine design. Using
>> zend_compile (or a derived implementation) may help.
>
> Is there a technical problem with code located outside of definitions, or=
 is it just a convention (PSR already contains this rule) ? I understand th=
e problems it poses in HHVM, but I don't see why we should check that with =
the engine as it is structured now. Even if we can detect such questionable=
 usage (and we can detect it quite easily just using tokenizer output), IMO=
, we are not responsible of what developers put in their scripts.

I was too vague.

If some code is loaded and part of it will be always executed even if
not used at all in a request, this will have side effects. Also
besides the impact of having code being ran on each request, I do not
think it is good idea to being to have top context running code, at
all :)

Cheers,
--=20
Pierre

@pierrejoye | http://www.libgd.org