Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63706 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44899 invoked from network); 29 Oct 2012 20:26:18 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Oct 2012 20:26:18 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.143 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.143 smtp143.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.143] ([67.192.241.143:53767] helo=smtp143.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/01-31721-966EE805 for ; Mon, 29 Oct 2012 15:26:18 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp24.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id B6F3E180703; Mon, 29 Oct 2012 16:26:14 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp24.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 5E2FE180119; Mon, 29 Oct 2012 16:26:14 -0400 (EDT) Message-ID: <508EE666.70206@sugarcrm.com> Date: Mon, 29 Oct 2012 13:26:14 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Clint Priest CC: David Muir , Pierre Joye , "internals@lists.php.net" References: <508A68B9.1050801@zerocue.com> <508AA48D.5010903@sugarcrm.com> <508C1C4F.6060406@zerocue.com> <508D5726.8080200@zerocue.com> <508DE27C.4040007@gmail.com> <508DE94E.30103@zerocue.com> In-Reply-To: <508DE94E.30103@zerocue.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Property Accessors v1.2 : isset / unset "failable" From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Is there another class of error that would make more sense? Don't most > people turn off E_NOTICE errors? Perhaps emit an E_STRICT? I always run with E_NOTICE in development, that's kind of what E_NOTICE is for :) I don't think isset() should produce any warnings/notices - this is how it is now in PHP. Otherwise there's no point in having isset() operation - you can check for NULL with read, whole point of isset() is that you're checking both for read legality and read result, and it's guaranteed not to be issuing warnings if this variable doesn't exist (while reading may issue warnings). -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227