Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:49902 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33688 invoked from network); 12 Oct 2010 16:54:26 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Oct 2010 16:54:26 -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.123 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.123 smtp123.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.123] ([67.192.241.123:55143] helo=smtp123.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/B5-34267-1C294BC4 for ; Tue, 12 Oct 2010 12:54:26 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp22.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 19CDF17016E; Tue, 12 Oct 2010 12:54:23 -0400 (EDT) X-Orig-To: sv_forums@fmethod.com X-Orig-To: internals@lists.php.net X-Virus-Scanned: OK Received: by smtp22.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id CBBD6170313; Tue, 12 Oct 2010 12:54:22 -0400 (EDT) Message-ID: <4CB492BE.2090305@sugarcrm.com> Date: Tue, 12 Oct 2010 09:54:22 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4 MIME-Version: 1.0 To: Stan Vass CC: "internals@lists.php.net" References: In-Reply-To: Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Process failed? BC and use cases for property_exists() broken in PHP 5.3 From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > 3) The use case for this function required the existing behavior > (i.e. can you safely call property $x from the current scope with no > warning?), and that *ignored* when the behavior was changed. We > already have Reflection classes for inquiring protected/private > properties of a class from any scope. Maybe we can fix this by having an argument to the function that if false, checks only for existence, and if true, checks also for access? On the other hand, we already have isset() for vars and is_callable() for methods, so this use case might to be covered. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227