Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113899
To: internals@lists.php.net
References: <c-17aa9-kmym40m7-tisanx=k89cku@2.gethop.com>
 <CAJpLVh2gJV7LcJUJaAQ6F4LOnbJVBKSzS0rT1B_Xc_xNgbkvSw@mail.gmail.com>
Message-ID: <81ecea3e-271e-6767-a7cb-4c56829412b0@processus.org>
Date: Thu, 1 Apr 2021 11:45:34 +0200
MIME-Version: 1.0
In-Reply-To: <CAJpLVh2gJV7LcJUJaAQ6F4LOnbJVBKSzS0rT1B_Xc_xNgbkvSw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Subject: Re: [PHP-DEV] Why is assert limited to a debugging feature only?
From: pierre-php@processus.org (Pierre)

Le 01/04/2021 à 10:50, Olle Härstedt a écrit :
> Dunno about the motivation of the implementors, but usually assertions
> are used for internal invariants and mental checks while exceptions
> should be used for interaction with the outside world (database
> errors, user input errors etc). If you follow this, an assert error
> will never be useful for a user, it will always be an "internal
> error", and that's why it can (should?) be disabled in production.
>
> Olle

Hello,

I don't know about the original motivations either, but at work we 
mostly use to force IDEs to understand types where PHP can't enforce 
them, due to its highly dynamic nature and lacks of generics. Most of 
our assert usage as like this: \asset($foo instanceof Bar);

We never enable those on production, we have assert() calls pretty much 
everywhere and they don't serve any other purpose than being explicit 
for the code readers and IDE and we use them for debugging purpose: it 
raises exceptions for developer preventing them to proceed further until 
they fixe the bugs, but they don't break the production.

Regards,

--

Pierre