Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79877
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH4gyTXFFYZ=-UR2KJ2y3PHzX32zqSbmwNHRqAQrC4CxaA@mail.gmail.com>
References: <000c01d01ca0$7e70c850$7b5258f0$@yahoo.fr> <CAH-PCH4gyTXFFYZ=-UR2KJ2y3PHzX32zqSbmwNHRqAQrC4CxaA@mail.gmail.com>
Date: Mon, 22 Dec 2014 23:40:33 -0200
Message-ID: <CAFp73Xs55kC8xEYL2stx24YfoJESmR7zn42qrRUS_-rE8rtmdQ@mail.gmail.com>
To: Ferenc Kovacs <tyra3l@gmail.com>
Cc: nf.laupretre@yahoo.fr, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec5171e81105c77050ad844ad
Subject: Re: [PHP-DEV] Proposal for PHP 7 : case-sensitive symbols
From: guilhermeblanco@gmail.com ("guilhermeblanco@gmail.com")

--bcaec5171e81105c77050ad844ad
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1 for adding E_DEPRECATED and removing support in PHP 8.

On Mon, Dec 22, 2014 at 11:17 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

> On Sat, Dec 20, 2014 at 11:01 PM, F & N Laupretre <nf.laupretre@yahoo.fr>
> wrote:
>
> > Hi,
> >
> >
> >
> > I don't know if this was discussed before. So, tell me what you think
> > before
> > I write an RFC.
> >
> >
> >
> > I would like to propose that namespaces, functions, and classes become
> > case-sensitive (constants are already case-sensitive). Actually, I neve=
r
> > understood why they are case-insensitive. Even if the performance gain =
is
> > negligible, I think it could be the right time to question this.
> >
> >
> I think that the cost of that BC break is too high, and will only happen =
in
> an alternative implementation (if at all).
> Putting that aside, if we want to go down that road, we should first
> discourage people from such usage, and as we never did that(no E_STRICT n=
o
> E_DEPRECATED) it would be extremely rude to remove support for that in 7.=
0.
> I think that a Pull Request for adding E_STRICT or maybe even E_DEPRECATE=
D
> would have a chance of getting voted in but depends on the implementation
> and how much overhead would it cost.
>
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>



--=20
Guilherme Blanco
MSN: guilhermeblanco@hotmail.com
GTalk: guilhermeblanco
Toronto - ON/Canada

--bcaec5171e81105c77050ad844ad--