Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50478 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52621 invoked from network); 24 Nov 2010 19:02:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Nov 2010 19:02:51 -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.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.163 smtp163.iad.emailsrvr.com Linux 2.6 Received: from [207.97.245.163] ([207.97.245.163:48891] helo=smtp163.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2B/62-36251-9516DEC4 for ; Wed, 24 Nov 2010 14:02:51 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp46.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 4382FE879C; Wed, 24 Nov 2010 14:02:47 -0500 (EST) X-Virus-Scanned: OK Received: by smtp46.relay.iad1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id CCA26E8825; Wed, 24 Nov 2010 14:02:46 -0500 (EST) Message-ID: <4CED6155.1000606@sugarcrm.com> Date: Wed, 24 Nov 2010 11:02:45 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: Etienne Kneuss CC: "internals@lists.php.net" References: <1DFD5821-B2F2-4212-9CB1-8D434123B101@zort.net> <20101124173501.GB72409@croustillant.local> In-Reply-To: <20101124173501.GB72409@croustillant.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Add E_STRICT when defining a required function parameter after an optional parameter From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Given the semantics of PHP arguments, there is "nothing wrong" with > defining a required argument after an optional one, and in some cases > it is required. Consider: I think there's something wrong with it, primarily - the fact that it doesn't really make any sense. The object/null thing is a kludge. Unfortunately, I don't see a proper way to handle this without named arguments. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227