Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:81402
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.176 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <54CB13A4.9060900@rodas.me>
References: <54CB13A4.9060900@rodas.me>
Date: Fri, 30 Jan 2015 14:36:17 +0900
Message-ID: <CAGa2bXb+4QhH1NCYseELeHUATStB7a=MHxdaqY5ZFkfcQbXXNg@mail.gmail.com>
To: =?UTF-8?B?Q8Opc2FyIFJvZGFz?= <cesar@rodas.me>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c11a9838efd0050dd7fe04
Subject: Re: [PHP-DEV] Is it a good idea to have a "strict" mode?
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a11c11a9838efd0050dd7fe04
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Cesar,

On Fri, Jan 30, 2015 at 2:16 PM, C=C3=A9sar Rodas <cesar@rodas.me> wrote:

> 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.
> ```
>

We have error_reporting INI for this purpose.
Users may be strict or lazy for errors by the INI setting.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--001a11c11a9838efd0050dd7fe04--