Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83878
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.174 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <CA+9eiLt9YXo_OY1CEuNLXwTFoxRNZTy78Wj3mUmWdOEVeBMoVQ@mail.gmail.com>
References: <CAEbg-4aR14ispgwzBmYxC1oFWPpKgdXTTmVcwJs_vRESKSw81A@mail.gmail.com>
 <CA+9eiLt9YXo_OY1CEuNLXwTFoxRNZTy78Wj3mUmWdOEVeBMoVQ@mail.gmail.com>
Date: Thu, 26 Feb 2015 10:26:49 +0100
Message-ID: <CAMUwpuRBUeGVE=Wi2r53SO_MKCjK4ZinBF_SAZgiz+=uhqfZ+g@mail.gmail.com>
To: Dmitry Stogov <dmitry@zend.com>
Cc: Alexander Lisachenko <lisachenko.it@gmail.com>, PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b873ab068c6e0050ffa5cb2
Subject: Re: [PHP-DEV] [Discussion] Last chance for case-sensitive engine
From: jpauli@php.net (Julien Pauli)

--047d7b873ab068c6e0050ffa5cb2
Content-Type: text/plain; charset=UTF-8

On Wed, Feb 25, 2015 at 7:52 PM, Dmitry Stogov <dmitry@zend.com> wrote:

> Hi Alexander,
>
> On Tue, Feb 24, 2015 at 10:48 AM, Alexander Lisachenko <
> lisachenko.it@gmail.com> wrote:
>
> > Morning!
> >
> > I want to ask this question one more time before PHP7 feature freeze: can
> > we  the engine case sensitive from PHP>=7.0?
> >
> > There is a draft for that: https://wiki.php.net/rfc/case-sensitivity
> > (mostly empty), so I decided to ask this question in the internals mail
> > list.
> >
> > Pros: more simple O(1) hash table checks for properties, functions,
> > methods, classes without strtolower normalization on the engine/parser
> > level. Consistency with unicode class names (yes, they are case
> sensitive,
> > check http://3v4l.org/ia0pc), consistency with exisiting PSR0,4
> standards
> > (case sensitive mapping of class names to the file names)
> >
> > From my experience, all modern PHP framework don't use case-insensitive
> > code, so chance to break anything for them is really low.
> >
> > Cons: on the extension level things aren't so good and can be some BC
> > breaks (like with phpng)
> >
> > Possible ways:
> >
> > 1) Keep PHP engine case-insensitive for PHP7
> > 2) Make PHP engine case-sensitive since PHP7 with possible minor BC
> breaks
> > in the extensions (this breaks can be easily fixed)
> > 3) Add a compile-time switch, eg. --with-case-sensitivity to the
> > configuration to have an ability to build PHP with sensitivity and make
> > this option enabled by default since next major version (PHP>=8.0). Add
> > deprecation notices in 7.x
> >
> > Thoughts?
> >
>
> I case we would designed a new language I would rise two hands.
> Changing, syntax in an existent widely used language is an additional pain
> for users.
> Technically it shouldn't be very difficult to remove support for
> case-insensitivity, and it'll even improve speed and memory consumption,
> but I don't think it costs the compatibility break.
>
> Thanks. Dmitry.
>

I agree that doesn't seem like a reasonable idea.

Julien.P

--047d7b873ab068c6e0050ffa5cb2--