Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80295 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35347 invoked from network); 9 Jan 2015 02:36:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 9 Jan 2015 02:36:00 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@tekwire.net; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=francois@tekwire.net; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain tekwire.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@tekwire.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:20596] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B8/63-14400-A8E3FA45 for ; Thu, 08 Jan 2015 21:35:59 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id 41E654B022A; Fri, 9 Jan 2015 03:33:52 +0100 (CET) Reply-To: To: "'Pierre Joye'" , "'Fred Emmott'" Cc: "'Derick Rethans'" , "'PHP internals'" , "'Sara Golemon'" , "'Stanislav Malyshev'" , "'Benjamin Eberlei'" References: <54AAF98B.4020709@gmail.com> <001b01d029bb$fa687fc0$ef397f40$@tekwire.net> <31A3F47C-0C5B-46E0-8B34-2105F467FDB3@fredemmott.co.uk> In-Reply-To: Date: Fri, 9 Jan 2015 03:35:47 +0100 Message-ID: <007901d02bb4$f9ccca80$ed665f80$@tekwire.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKBrOMj1TuM8+kkOgWpn3PeY833kwGP3HvhATjV2lMChcgIAwHV7IBCAiSTtMcB5W5x9wGAwYgSArmKntoCEHaiZ5rIQ5+g Content-Language: fr X-Antivirus: avast! (VPS 150108-1, 08/01/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] [RFC] Extension Prepend Files From: francois@tekwire.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > 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. >=20 > 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 the 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. Regards, Fran=C3=A7ois