Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81421
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.173 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <54CB13A4.9060900@rodas.me>
References: <54CB13A4.9060900@rodas.me>
Date: Fri, 30 Jan 2015 11:46:28 +0100
Message-ID: <CAMUwpuRBBJkoPP6gEjVRAT5xxujOHPMb5ixsyhoZCkWw7Cx6Mg@mail.gmail.com>
To: =?UTF-8?B?Q8Opc2FyIFJvZGFz?= <cesar@rodas.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b86c8b8896424050ddc539d
Subject: Re: [PHP-DEV] Is it a good idea to have a "strict" mode?
From: jpauli@php.net (Julien Pauli)

--047d7b86c8b8896424050ddc539d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 30, 2015 at 6:16 AM, C=C3=A9sar Rodas <cesar@rodas.me> wrote:

> Hi!
>
> I'm wondering if it would be a good idea to have a `strict` mode in PHP.
> Many language have them and it is a good idea.
>
> I think it should be a bit different in PHP, it should encourage the
> following things:
>
>  - Avoid deprecated things, it should throw an exception.
>  - Avoid explicit conversions of undefined constants to strings.
>  - Anything else that could make run-time slower *or* bad practice.
>
> ```php
> "use strict";
>
> var_dump(FOOBAR); // should throw an exception, undefined constant.
> ```
>
> Good idea?
>


This has already been debated.

Use error_reporting instead. If you write "use strict;" in PHP, you'll hit
a meaningful error message btw ;-)

Also, syntax checks, etc... is the job of your IDE.
Mine already tells me many things about unused variables, etc...

Julien P

--047d7b86c8b8896424050ddc539d--