Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7567 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13979 invoked by uid 1010); 4 Feb 2004 19:39:46 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 13892 invoked by uid 1007); 4 Feb 2004 19:39:46 -0000 Message-ID: <20040204193945.13891.qmail@pb1.pair.com> To: internals@lists.php.net References: <5.1.0.14.2.20040204201046.06eae688@localhost> <20040204182514.GM5094@bumblebury.com> Date: Wed, 4 Feb 2004 11:39:45 -0800 Lines: 19 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Posted-By: 169.229.139.97 Subject: Re: [PHP-DEV] RC1 From: pollita@php.net ("Sara Golemon") > > (a) Failure return value of FETCH_RESOURCE and the default return value - > > should we change it to be FALSE? Today it's NULL, which is inconsistent > > with most of the functions in PHP which return FALSE on failure. The > > downside is that changing it may break scripts that check the return value > > with === or !== > > > > Should be NULL, not a boolean FALSE, IMNHO (*). False indicates the > given operation was not succesful but everything supplied was in valid > boundaries. At least that's how I see it, but PHP is across the board > inconsistent in this area, so I see no reason to break BC. > -1 for the reasons stated by Sterling above. -Sara