Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:94040
Return-Path: <pierre.php@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 27025 invoked from network); 16 Jun 2016 08:17:48 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
by localhost with SMTP; 16 Jun 2016 08:17:48 -0000
Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.48 as permitted sender)
X-PHP-List-Original-Sender: pierre.php@gmail.com
X-Host-Fingerprint: 209.85.218.48 mail-oi0-f48.google.com
Received: from [209.85.218.48] ([209.85.218.48:34998] helo=mail-oi0-f48.google.com)
by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
id F0/10-25388-BA062675 for <internals@lists.php.net>; Thu, 16 Jun 2016 04:17:47 -0400
Received: by mail-oi0-f48.google.com with SMTP id w5so57885256oib.2
for <internals@lists.php.net>; Thu, 16 Jun 2016 01:17:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc;
bh=jSGyr//9QBhtS1Al6NntVaX98W+iuiL3cqT1Cko9HYw=;
b=d9t+9lojpB0bWPLVdRkA+yPsrr1Zf7mWBzpvMctQvjWtpy4hsXc7USPBHvIDRP6Jj6
C5djL+lhzSLNTgTeCWLRrjxIGt8kfm9zMLojT2nRcFFE49wjvmcaA0PP83kTSL5qXM7C
R2oZdnrsPEapZeCIk7xiMmm+UrqaMGrqjFQ1mm8eoOJ334wTXoCzvgSPkUK8baUpetPy
K2cdG+Zoia3Ag4TGWgHTnZzS/nTIPmYtGYFxOQozgOZnAtBk1kuIn8NXziVop2QGRROF
qcFcpD3bGlLX3acawershUpM9yZ5u+erQC1m0hCUcYdBffhQoDDMW0o4WMZvhfiYHJqN
ImaQ==
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;
bh=jSGyr//9QBhtS1Al6NntVaX98W+iuiL3cqT1Cko9HYw=;
b=iwTeYSMisT6vjNZx6VPX6icMjGk3XTJXDa/T00dcWelEuq2bLDYzPGE+JLQAhZO01U
eONVd+wfUasrwakB/54MAeNeqS0QqEMwxLpuy4RM4aEp6k/BByy+4ww0LQCJbUKBM0Sz
AQIuhPyzC+aPwL/ZrF7Jj/2EaqqAEnJg2rNMCpEStoTBGcz4fA2e3K+JC6z656w2EMQO
Ie1Vsx5NmYq3zuySlY5nJp1I5umbvCC91H3NcMXK5n54rHQXzdaP1YjQZ9wd1BnH7RYH
JID14a/ZhE1wUtVHax4V6DH/oJmuf/i6Gdpe+4HRnTHPW1vUbrg6vSYQWonvjbvdYIN6
5Arw==
X-Gm-Message-State: ALyK8tLS34I/0DBfiM4xK9Wc+79wF2RsHgXKVSUYawDgKWJ/tLAWM5tKb+S1HX90pWA/W5VzkssxTGSsJobmKQ==
MIME-Version: 1.0
X-Received: by 10.202.237.144 with SMTP id l138mr1605931oih.200.1466065063452;
Thu, 16 Jun 2016 01:17:43 -0700 (PDT)
Received: by 10.202.108.197 with HTTP; Thu, 16 Jun 2016 01:17:43 -0700 (PDT)
Received: by 10.202.108.197 with HTTP; Thu, 16 Jun 2016 01:17:43 -0700 (PDT)
In-Reply-To: <BY2PR0201MB1784B29547CD35B1FE04B3ACBF500@BY2PR0201MB1784.namprd02.prod.outlook.com>
References: <BY2PR0201MB1784853FB024646DE2CE2E84BF500@BY2PR0201MB1784.namprd02.prod.outlook.com>
<CAFMT4NqzMgOq6-MWpwKZLGyEo=Sr7Swf7PviM_XgMgMkN3w46A@mail.gmail.com>
<BY2PR0201MB1784B29547CD35B1FE04B3ACBF500@BY2PR0201MB1784.namprd02.prod.outlook.com>
Date: Thu, 16 Jun 2016 15:17:43 +0700
Message-ID: <CAEZPtU5v+0X3_KPuxiEwx9LLayo7VOaMepZ-0KR+WE=z9xP5kg@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: PHP internals <internals@lists.php.net>, Levi Morrison <levim@php.net>
Content-Type: multipart/alternative; boundary=001a113d2f8e5328b5053560df16
Subject: Re: [PHP-DEV] [RFC] Throw Exception on Attempt of Constant Redefinition
From: pierre.php@gmail.com (Pierre Joye)
--001a113d2f8e5328b5053560df16
Content-Type: text/plain; charset=UTF-8
On Jun 11, 2016 4:27 AM, "Dmitry Stogov" <dmitry@zend.com> wrote:
>
> In general, you are right, but this is possible only if application
ignores Error exceptions...
Exactly.
Many if not hundred of applications do not even use exception but if a
couple of places, let alone plug-ins for these apps.
Most of these apps is what I called main stream applications. They are
provided as SaaS or ready to be installed. The providers taking care of the
system parts, php included.
Now what will happen if they update and exception start to be throw for
that?
Right, they will downgrade or not update at all for the good ones (tested).
To me it sounds like a pretty bad plan to ease the migration path.
In other words, it looks to me that you are working on something bigger,
early phase. This things seems to require more and more clean paths and
rules.
This is alone is something to justify to start to plan 8. And we all know
Jit will be for 8. Let start even if the Jit itself is not even officially
started.
--001a113d2f8e5328b5053560df16--