Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:69155 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77296 invoked from network); 16 Sep 2013 20:35:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Sep 2013 20:35:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@golemon.com; spf=softfail; sender-id=softfail Authentication-Results: pb1.pair.com header.from=php@golemon.com; sender-id=softfail Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.160.42 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.160.42 mail-pb0-f42.google.com Received: from [209.85.160.42] ([209.85.160.42:48310] helo=mail-pb0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 18/83-57385-4AB67325 for ; Mon, 16 Sep 2013 16:35:49 -0400 Received: by mail-pb0-f42.google.com with SMTP id un15so4577651pbc.1 for ; Mon, 16 Sep 2013 13:35:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=xr96JR6sc9Oq4NIumAcsz2QzPoJaPiKZblTuXXUZxDQ=; b=E7Qip+y3C1thgQnuIj5FVeF827HCmrbQrIyBfUzJw+mJdUM8aGH9PSeoHW44L5LA8o 4kufOWj8Rj5sCORxnpd89BCnKPYOiltDPIxR7btKWcvtd7NSPmooDoSVQ3lhV0RBzxtH 11tMSavav04wt1qO5KUu0bFZbDd3WN6qXPyLEabIzhv/KxzS92q9n+kgKjO7s3dRpIEJ Tic2bFgw/ZgjqRYKKeQYE7wnC/X/UqmxbiLP3R/k2afAT0h1gno7xFYvGxzKtBiIdmfs 72g4s4HysdMfJ62xRApVu4peiSsE3vz+jNiDZJuyGog9L4vMqRH5Ax71Kbe5Im5d5zD0 vwkg== X-Gm-Message-State: ALoCoQn/XN0J6DsVoTl7EVoznZgDRnGp1tcB4U5M9wwiwyi0Z83GXf0I/woRIFhKIMY9sMZpQs1t MIME-Version: 1.0 X-Received: by 10.66.217.166 with SMTP id oz6mr33088643pac.22.1379363745522; Mon, 16 Sep 2013 13:35:45 -0700 (PDT) Sender: php@golemon.com Received: by 10.70.24.33 with HTTP; Mon, 16 Sep 2013 13:35:45 -0700 (PDT) X-Originating-IP: [2620:0:1cfe:18:22c9:d0ff:fe87:295b] In-Reply-To: References: Date: Mon, 16 Sep 2013 13:35:45 -0700 X-Google-Sender-Auth: -PjJbnbb6KOO2tFrOBOhJev37OA Message-ID: To: Nikita Popov Cc: PHP internals Content-Type: multipart/alternative; boundary=047d7b5d9fa911843604e68626a9 Subject: Re: [PHP-DEV] Re: [RFC] Syntax for variadic functions From: pollita@php.net (Sara Golemon) --047d7b5d9fa911843604e68626a9 Content-Type: text/plain; charset=ISO-8859-1 > Assuming the RFC as-is represents the current state, I'm +1 on all of it. >> >> I'm not a fan of some of the proposed alterations which would translate >> arrays (a la call_user_func_array()). To clarify, the following output is >> what I'd expect: >> function f(...$args) { >> echo count($args); >> } >> f(1,2,3); // 3 >> f([1,2,3]); // 1 >> >> Not "3" in both cases. >> > > Yes, that's the output you'll get. If it weren't the case it would be > impossible to define a function accepting multiple array arguments like > f([1, 2, 3], [4, 5, 6], [7, 8, 9]). > > Right, that was exactly the ambiguity I was unfond of. Glad that was as I hoped. Voted +1. --047d7b5d9fa911843604e68626a9--