Re: About declare(strict_types = 1)
| From: | Pavel Kouřil | Date: | Mon, 16 Mar 2015 22:11:41 +0000 |
| Subject: | Re: About declare(strict_types = 1) | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-85101@lists.php.net to get a copy of this message | ||
On Mon, Mar 16, 2015 at 11:04 PM, Pierre Joye <pierre.php@gmail.com> wrote:
>
> On Mar 16, 2015 11:16 PM, "Pavel Kouřil" <pajousek@gmail.com> wrote:
>
>> I can't speak for anyone who voted, but personally, if I could vote, I
>> would voted "no" - not because "I don't want to block people from
>> getting what they want", but because I sincerely think that having ANY
>> setting that changes code's behavior is bad in the long run (and that
>> removing the feature might not be really easy, once people realize
>> that the feature is really bad, as people realized with safe_mode and
>> register_globals after few years).
>>
>> I work on multiple projects for multiple clients - some have great
>> code base, some have a bad one. Different typing contexts in different
>> projects isn't going to help anything at all - it will only bring a
>> mental overhead.
>
> So you would have voted no on namespaces?
You will probably have to try to explain the similiarity between a
setting that conceptually changes how language works and namespace. I
guess Derick wanted to do so, but his example doesn't make sense and I
didn't understand it, tbh.
Regards
Pavel Kouril