Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80237 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69812 invoked from network); 6 Jan 2015 14:53:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jan 2015 14:53:10 -0000 Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 74.125.82.182 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 74.125.82.182 mail-we0-f182.google.com Received: from [74.125.82.182] ([74.125.82.182:62648] helo=mail-we0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 13/51-61664-3D6FBA45 for ; Tue, 06 Jan 2015 09:53:08 -0500 Received: by mail-we0-f182.google.com with SMTP id w62so9767762wes.41 for ; Tue, 06 Jan 2015 06:53:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=NS9zYdTiFhUOF3dJPO46WDCv0/AI0IQAEPejOECvZno=; b=m7RRG4Fm1yiHWc+bUYUNGILZn3BBNoG1Jgtw1VSjrS2ByaSqhWN58jBiZc08Lj0krV WCXMkzENfF5vyZIox1QTFPPAQQJ8cP3tl0C9ttaKrGYXFcJaBkTloD5mEZ4J6it9dIhf WAfL1VB7y0o8HcO+DpeCpehOMnlYRXMvLMwgvH8mU9nc7dY9MWvWM7VUDq0mAlJdrPBk YbUd9CB+APRqBE9wJHRPS2f7Q5k4B9hxj7yyeigH4JioYZ+/DJqV4KSfwXlAnSOTuDmW ZRaq813YhDYQjvOsB6icr9StTp6xdnJbYIjxG+nG4GZlj2CAjr0/w2RsoqeBEX62q8Y5 evag== X-Gm-Message-State: ALoCoQnDDhiY1rn5qJQ2q5g7hejnwkg9BxPf3KoO9OsrOP6S8o0z0q0V9hnWSlmoNTQB9tzbhemo MIME-Version: 1.0 X-Received: by 10.180.91.36 with SMTP id cb4mr37100037wib.30.1420555985092; Tue, 06 Jan 2015 06:53:05 -0800 (PST) Received: by 10.194.57.73 with HTTP; Tue, 6 Jan 2015 06:53:05 -0800 (PST) X-Originating-IP: [77.11.82.73] In-Reply-To: References: <54AAF98B.4020709@gmail.com> <001b01d029bb$fa687fc0$ef397f40$@tekwire.net> Date: Tue, 6 Jan 2015 15:53:05 +0100 Message-ID: To: Pierre Joye Cc: francois@tekwire.net, PHP internals , Sara Golemon , Stanislav Malyshev , Derick Rethans Content-Type: multipart/alternative; boundary=f46d043d6711e01736050bfcf6fb Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files From: kontakt@beberlei.de (Benjamin Eberlei) --f46d043d6711e01736050bfcf6fb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jan 6, 2015 at 3:50 PM, Pierre Joye wrote: > > On Jan 6, 2015 9:20 PM, "Fran=C3=A7ois Laupretre" = wrote: > The whole code to consider as part of an extension, whatever the language= , > must be kept in sync. And the best way to achieve this is to store it in = a > single file. > > I would rather say in a single release and package. Built in scripts in a= n > extension is an extremely bad step, maintenance, issues management and al= l > possible complications to allow that may bring. But we get each other vie= w. > I only hope we will not do that. > > Also interesting to ignore the other questions, which are imho very > critical. :) > How is shipping php code inside so/ddl worse than shipping just the C code this way? I agree with you it makes changing the PHP code more difficult (requires recompile), but it makes the deployment and build much simpler. Including the security concerns. > > Regards, > > > > Fran=C3=A7ois > > > > > > > > > --f46d043d6711e01736050bfcf6fb--