Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:84072 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62519 invoked from network); 28 Feb 2015 08:19:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Feb 2015 08:19:01 -0000 Authentication-Results: pb1.pair.com smtp.mail=francois@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=francois@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 212.27.42.2 as permitted sender) X-PHP-List-Original-Sender: francois@php.net X-Host-Fingerprint: 212.27.42.2 smtp2-g21.free.fr Received: from [212.27.42.2] ([212.27.42.2:56324] helo=smtp2-g21.free.fr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 06/60-59402-4F971F45 for ; Sat, 28 Feb 2015 03:19:01 -0500 Received: from moorea (unknown [82.240.16.115]) by smtp2-g21.free.fr (Postfix) with ESMTP id C213D4B0283; Sat, 28 Feb 2015 09:18:32 +0100 (CET) Reply-To: To: "'Benjamin Eberlei'" , "'Lester Caine'" Cc: "'PHP Internals'" References: <54F077B2.3020103@lsces.co.uk> In-Reply-To: Date: Sat, 28 Feb 2015 09:18:51 +0100 Message-ID: <0bc501d0532f$2f829640$8e87c2c0$@php.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHbEgvqZ08kgCvmYfG4mXODzCFejgH/2bYmAiIqy+UCGOa2ZQKfmc2ZnKliduA= Content-Language: fr X-Antivirus: avast! (VPS 150227-0, 27/02/2015), Outbound message X-Antivirus-Status: Clean Subject: RE: [PHP-DEV] Coercive STH - some real world tests and updated RFC From: francois@php.net (=?utf-8?Q?Fran=C3=A7ois_Laupretre?=) > De : Benjamin Eberlei [mailto:kontakt@beberlei.de] > > Interestingly functions like is_infinite(), is_dir(), is_file() all = expect > correct types like float or string here although from the naming = convention > "is_something" i would expect it says just false on *anything* else = (which > it almost does right now). Agreed. Must be modified. Even for 7.0 if it can be approved before = freeze. All is_xxx functions must be checked and made more permissive on = input arg (most, if not all, should probably accept any zval, minor BC = break). > Imho the problem is that the return values of php internal functions = being > string|false will lead to massive consecutive errors when passing this = on > to other internal unctions. Right. A side effect of the RFC is to encourage for an explicit check of = false. May I say that this won't exactly lead to 'errors', as we are = just deprecating usage of the implicit cast in such case. So it may lead = to massive 'deprecated' messages but, apart from additional messages, = behavior won't change. Regards Fran=C3=A7ois