Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:93297 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33863 invoked from network); 12 May 2016 22:41:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 May 2016 22:41:24 -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.215.65 as permitted sender) X-PHP-List-Original-Sender: php@golemon.com X-Host-Fingerprint: 209.85.215.65 mail-lf0-f65.google.com Received: from [209.85.215.65] ([209.85.215.65:36264] helo=mail-lf0-f65.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AE/29-28272-39605375 for ; Thu, 12 May 2016 18:41:24 -0400 Received: by mail-lf0-f65.google.com with SMTP id y84so8944800lfc.3 for ; Thu, 12 May 2016 15:41:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=golemon-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-transfer-encoding; bh=Hl23EXVajo7KgC+tr4ubkX+TFiJS2EN5K9KuchSDvy8=; b=YErl2OQKzRINLjQBPO/37fAf6BaaOYDkbxgCKdvoyz547Anx1PnICrxrnZQ/hNOR9Y uz8+pq41cEAJeIPeX4+maS/uO3xu+fQWk3j3kCKcLBfPDP9NYoM6wN78GizPQBetUQzH iqryP2VRaVFjtW1BxNXdaRaolZ6zKfcPyLpWrDYgoqkJprsk0nnGuB+yAwS7p6e+E/Ti eqD+9ZPkXqkDh9t8jdfWbZFJGdYoMiAK4xQvCzccAVu7KHSc8jH05upZwkmVhivfenSF QK6d9nlgFvNNAcDgQmpfm4jHTuj2MUU44aL23WA5jMx2OhjgZIBXRD2rbdKdEZaEZniH BqoA== 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-transfer-encoding; bh=Hl23EXVajo7KgC+tr4ubkX+TFiJS2EN5K9KuchSDvy8=; b=TC/Usnfk56hcl5VeB4sJuFM7Ts4XEkZZ2ySj/9HNtuQ70mnkBLeUZNRYJSOGZ3sOiq nS8N6w7mLaeUQJQ14P1UAvCTdiWHWRY53yUIWCOEdaqZzIsR5Cmk08N1XANxToH4dKEz msVdh6xAdBDb/OrmjKq3L+iP5o7ztjzyinVj9NyZrJWjG4esK5tnc36TyOWvo4LMlqYA QswstygVr3EOfzKKjzi/8dZb5GdKdf4Ykjb9qxs+gpJyl6BhUn++nYiVr1Fsf0dO5WJX ftjNTppUXbkVs0HWG1mqh19Z7X+Wdk7F9oGZpeYA8bvtIUldt1F/x+LBCuexRCd8h0N8 sJRQ== X-Gm-Message-State: AOPr4FXQrEnjdqyzwUOLl98GA0R/Bk+4/vSg8miX4SC8YxioMIXc8QIOFZZ93r7OxGDzRJ1j5t6/dBP9nqx3WQ== MIME-Version: 1.0 X-Received: by 10.25.20.78 with SMTP id k75mr4609195lfi.82.1463092881038; Thu, 12 May 2016 15:41:21 -0700 (PDT) Sender: php@golemon.com Received: by 10.112.19.72 with HTTP; Thu, 12 May 2016 15:41:20 -0700 (PDT) X-Originating-IP: [107.198.91.68] In-Reply-To: <879feadf-c04e-c0de-826b-110b3eb4e22f@php.net> References: <452ddb93-1f47-1d0f-4f24-bedbff506b27@gmail.com> <98.61.11104.A1D41375@pb1.pair.com> <7c94ca37-e188-dd2b-a66f-bb63bf03041a@gmail.com> <1463008795.1856219.605250569.74618FC4@webmail.messagingengine.com> <92E7F8A8-0845-48A7-91B1-9554C5F66C9D@zend.com> <879feadf-c04e-c0de-826b-110b3eb4e22f@php.net> Date: Thu, 12 May 2016 15:41:20 -0700 X-Google-Sender-Auth: xsEFp9zly4d3jx4rEZfOjZXgDIw Message-ID: To: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= Cc: Zeev Suraski , Quim Calpe , "davey@php.net" , Larry Garfield , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Pipe Operator From: pollita@php.net (Sara Golemon) On Thu, May 12, 2016 at 11:52 AM, Fran=C3=A7ois Laupretre wrote: > If we restrict usage to function calls, we can quite easily get rid of th= e $$ by > associating to each function the position where the lhs must be inserted > when used as a 'piped function call'. > So we'd have to audit all 4k+ functions in the PHP runtime (and provide a mechanism for defining it on userspace functions)? That feels like a LOT of work for an alternate approach to something which takes much less work as proposed. I'm hoping I misunderstand what you're suggesting... > Getting rid of the $$ would resolve most issues about parameter order in = the > existing library, which is probably the biggest PHP sadness. > I will admit that anything which alleviates the sadness from argument ordering in the standard lib will be nice. I'm just skeptical of the work it'll take to get there. > My question, before I write a detailed proposal for this, is : do you wan= t > to keep the possiblility to use *any* expression between pipe operators, = or > would it be acceptable to restrict this to function calls? > I'd like to keep the ability to use arbitrary expressions as it keeps the language overall more consistent. That said, nothing is set in stone and the point of a discussion period is to discuss. Maybe with your proposal written out it'll make more sense to me. -Sara