Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55501 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30376 invoked from network); 18 Sep 2011 18:02:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Sep 2011 18:02:05 -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 207.97.245.193 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.193 smtp193.iad.emailsrvr.com Linux 2.6 Received: from [207.97.245.193] ([207.97.245.193:59158] helo=smtp193.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CA/10-28880-612367E4 for ; Sun, 18 Sep 2011 14:02:02 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp39.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id DA517989D9; Sun, 18 Sep 2011 14:01:53 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp39.relay.iad1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 2C4B8989D5; Sun, 18 Sep 2011 14:01:52 -0400 (EDT) Message-ID: <4E76320F.6010904@sugarcrm.com> Date: Sun, 18 Sep 2011 11:01:51 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 MIME-Version: 1.0 To: Derick Rethans CC: "RQuadling@GMail.com" , PHP internals References: <4E74E5A0.2030006@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] __constructor parameter limitations. From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! On 9/18/11 8:09 AM, Derick Rethans wrote: > If you don't want those warnings, turn them off! That's why there is a > specific error level for it. 1. It's not possible to turn these specific warnings off. The error level turns off all warnings on the level, not just specific ones. 2. These warnings don't warn about anything useful. There's no problem there to warn about. 3. Some of them aren't actually a warnings but fatal errors. Example: abstract class BaseClass { abstract public function foo(Type1 $foo, Type2 $bar); } class ExtendedClass extends BaseClass { public function foo() { } } This doesn't make sense on two levels: there's no reason why I can't extend foo() this way and there's no reason why abstracts are treated differently from non-abstracts. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227