Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68747 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74059 invoked from network); 30 Aug 2013 17:45:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Aug 2013 17:45:54 -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 108.166.43.107 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.107 smtp107.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.107] ([108.166.43.107:43475] helo=smtp107.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B2/F8-32511-15AD0225 for ; Fri, 30 Aug 2013 13:45:54 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 0212998097; Fri, 30 Aug 2013 13:45:51 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 69335981AB; Fri, 30 Aug 2013 13:45:50 -0400 (EDT) Message-ID: <5220DA50.9020306@sugarcrm.com> Date: Fri, 30 Aug 2013 10:45:52 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Nikita Popov CC: PHP internals References: <5220CEDE.8080600@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Argument unpacking From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Assuming you mean call_user_func_array, yes. This is just syntax sugar > for call_user_func_array. Advantages of this syntax over cufa are > outlined here: > https://wiki.php.net/rfc/argument_unpacking#advantages_over_call_user_func_array The only case that I see that could make sense is $db->query($query, ...$params). Multiple unpackings make no sense to me, as it is impossible to know which argument ends up where and no corresponding syntax exists on function side. Also, no other language as far as I can see allows it. Also, I just noticed the RFC tries to sneak in the exception throwing in the syntax construct, which we agreed not to do a long time ago and which was never done in the engine. We shouldn't do this - if you want to change PHP error handling, it should be in separate RFC for this purpose. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227