Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:123444
Date: Tue, 28 May 2024 11:58:43 +0000
To: Daikaras <webmaster@daikaras.lt>
Cc: PHP internals <internals@lists.php.net>
Subject: Re: [PHP-DEV] [RFC] Transform exit() from a language construct into a standard function
Message-ID: <OkIgWqyWoqaKFT3OGO6HJ8Xdb-6KjUgH5cqUxMhJIjtgGPszYrC2S6wK4S-INUfWOZ6ATY35fU5nALMdNmDUPrj7bsPIHZvZSp7WArlD2vo=@gpb.moe>
In-Reply-To: <c9656b3c-0454-48a0-97ee-91d962b54b00@daikaras.lt>
References: <GUMp_LJKefk4aLz9P9MA-zonKuik6uUNWZTtOAx-IeIhjPFsgfT3HHECPpyGF_ujq-LxI6tzBxMYgL5CMVGRkyzxSugweKix_YUGo2rXnb4=@gpb.moe> <c9656b3c-0454-48a0-97ee-91d962b54b00@daikaras.lt>
Feedback-ID: 96993444:user:proton
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: internals@gpb.moe ("Gina P. Banyard")

On Tuesday, 28 May 2024 at 07:53, Daikaras <webmaster@daikaras.lt> wrote:
>=20
> I feel like the reasoning in this RFC is misguided. `exit` behavior is
> not consistent with functions because it is not a function. But it is
> consistent with constructs like `echo`. Or am I wrong? I'm all for
> stricter typing but not at a cost of reliability. `exit` IMO should
> always terminate script, no exceptions (no pun intended :)). Otherwise,
> it may have security implications in some codebases, as Saki pointed
> out. So I'd rather have it error fatally like for example `break` does
> when passed non-integers. And on the same note maybe syntax could be
> improved to not require parentheses when passing the code (so `exit 0;` w=
ould be valid) since it seems to be the cause of the confusion.
>=20
> Just my 2c.
>=20
> p.s. In B/C table you should mention that passing Stringable objects
> will throw TypeError when `strict_types` are enabled.

This is not the cause of my confusion.
If you had read the RFC carefully, you would have seen that exit() already =
throws a TypeError that can be caught if you pass in a non-stringable objec=
t.
So the argument that it should always exit is invalid.

Moreover, in other programming languages exit() is a function, and I don't =
see a reason for having something be a language construct when there is no =
need for it.

Best regards,

Gina P. Banyard