Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104275 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 57432 invoked from network); 7 Feb 2019 12:36:14 -0000 Received: from unknown (HELO mail.gna.ch) (62.12.172.119) by pb1.pair.com with SMTP; 7 Feb 2019 12:36:14 -0000 Received: from [10.0.1.55] (77-56-180-37.dclient.hispeed.ch [77.56.180.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by darkcity.gna.ch (Postfix) with ESMTPSA id 7F7C120F5D; Thu, 7 Feb 2019 10:17:49 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\)) In-Reply-To: Date: Thu, 7 Feb 2019 10:17:49 +0100 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <38CCB7C0-C97D-41F1-8EB7-BA5FE8FD01F5@cschneid.com> References: To: Benjamin Morel X-Mailer: Apple Mail (2.3445.102.3) Subject: Re: [PHP-DEV] Don't silence fatal errors From: cschneid@cschneid.com (Christian Schneider) Am 07.02.2019 um 10:01 schrieb Benjamin Morel = : > IMO, @ can be safely removed the day PHP converts current warnings to = exceptions. Please don't do that either, I don't want to convert @mkdir("foo"); to try { mkdir("foo"); } catch (Exception $e) {} just to stop my script from exiting if the directory already exists. - Chris