Re: Deprecate and remove case-insensitive constants?
| From: | Levi Morrison | Date: | Tue, 12 Sep 2017 20:35:51 +0000 |
| Subject: | Re: Deprecate and remove case-insensitive constants? | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-100551@lists.php.net to get a copy of this message | ||
On Tue, Sep 12, 2017 at 11:59 AM, Rowan Collins <rowan.collins@gmail.com> wrote:
> On 12 September 2017 17:45:46 BST, Levi Morrison <levim@php.net> wrote:
>>The rest of my message only makes sense once you understand I was
>>proposing unified case sensitivity for all symbols *and* merging them
>>into one table.
>
> Ah, OK, so I partially missed the point. I'm still not sure what you're suggesting is
> sensible, though...
>
>
>>> If we want function and class references, they should have their own,
>>>unambiguous, syntax.
>
> I stand by this assertion. Consider the following statement:
>
> $foo = bar;
>
> Even if "bar" cannot *simultaneously* be the name of a function, a class, and a
> constant, it can still *potentially* be any of the three, from the point of view of the compiler.
If it's known, it's known, and it can proceed with that type. If it's
not known then autoload and proceed like normal. I fail to see how
this is an issue, and in fact, see it as a *significant* improvement
to our current situation...