Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:111100
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
In-Reply-To: <CAAKU0u=wAFKpJx28xCfg4k+-VEYRU-Cte+qvSR-idVC4rCoV9w@mail.gmail.com>
Date: Wed, 22 Jul 2020 10:48:06 +0200
Cc: internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <27E12C8A-3068-4EE2-BC84-B43C8D74A858@stitcher.io>
References: <CAFMT4Nrnn3tvPd9jZCBg3okEuo7YKjqwXUy-vKW4WFLbpqwm4A@mail.gmail.com>
 <CAAKU0u=wAFKpJx28xCfg4k+-VEYRU-Cte+qvSR-idVC4rCoV9w@mail.gmail.com>
To: Levi Morrison <levi.morrison@datadoghq.com>
Subject: Re: [PHP-DEV] Changing default assertion mode to throw exceptions
From: brendt@stitcher.io (Brent Roose)

Hi Levi

I personally almost never use assert, and actually assumed it would =
throw an error, so this sounds like a good change!=20

Have you done research on how this would affect the top-1000-ish popular =
packages like Nikita does?

Kind regards
Brent

> On 20 Jul 2020, at 15:48, Levi Morrison via internals =
<internals@lists.php.net> wrote:
>=20
> On Mon, Jul 13, 2020 at 11:37 AM Levi Morrison <levim@php.net> wrote:
>>=20
>> Hello everyone,
>>=20
>> I'd like to change the default mode of assertion failures to throw.
>> The current default is to warn. In my opinion this is a bad strategy:
>> the engine asserted that something that is expected to be true is =
not,
>> so executing further is a bad idea. This leaves throwing or bailing
>> out. I think throwing an exception is better than bailing out, so
>> that's what I propose.
>=20
> Hello, everyone. It's been a week and I have only heard a bit of
> positive feedback and no pushback. Anyone else want to reply?
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: https://www.php.net/unsub.php
>=20