From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: (qmail 4844 invoked from network); 25 Apr 2020 13:18:32 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with UTF8ESMTPZ; 25 Apr 2020 13:18:32 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id E9D129C8AF; Sat, 25 Apr 2020 23:18:31 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id E35839C733; Sat, 25 Apr 2020 23:18:16 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="tsUpqW9Y"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 5AF609C733; Sat, 25 Apr 2020 23:18:15 +1000 (AEST) Received: from mail-vk1-f175.google.com (mail-vk1-f175.google.com [209.85.221.175]) by minnie.tuhs.org (Postfix) with ESMTPS id EAAF99C171 for ; Sat, 25 Apr 2020 23:18:14 +1000 (AEST) Received: by mail-vk1-f175.google.com with SMTP id j1so3230135vkc.2 for ; Sat, 25 Apr 2020 06:18:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BUjNbpcIBlf1Gt1DEfVJH3fRxKlHT9J1/dulgqVq4U0=; b=tsUpqW9YqG2R7XlFkAWVkq7maKI66Fx41yMXaVk9XbXy9qVO5XzDkF/gfxGhomGF5z jx3l7tTiA6XLZoIFaS3wpjkZmOzv/B2UAK9ZQ40cnbCoLTVd/1NAfVuYpdWsSdcgJ/b7 CEwjWOGlC7KFLFEty0Il7ve7syJSixinZdg6AHQSXQyMIILIu06HthxIABkH24VeA2AZ z+iRzwqXwJaReA6wm5mrxHLX0OtPH2x8c3ZHR9z9V3JG8HuiaK+t15CNFyeqppEfDqKk 622zVcCcNhQRgGbdGlkVcHiZ2ao9VbxazoftuzLt9d6ID76HN76S7OrMKDWwRH41slM5 ahnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BUjNbpcIBlf1Gt1DEfVJH3fRxKlHT9J1/dulgqVq4U0=; b=kNHBT5WdJhSkie17nSfpbUwftYkS89tqcA5hp+FEU0tPNDn3xB1oqisf41ljgkd2Nj U31jXkMkEbmUEBu6kZcOZcbFN8vtl73ZCu+Mw4WwUQFRYm7J3sp2s8ri2G8lZgplHTKf FvpkZu0IBwZ5mGk1lWWlBWmDcDcoADusnIxKkijn2C14yHMItxq9oCprQxLMlj+Zkxds XqsSsmAhkUnuVdw31msbBi39TsgH2bHCx0jivRFQU+Fd0EWVpK9EbMEatdrIuxq0iW/R B5owu7QDL5T2Feis5eb7sA3FKOQvcYHoPKlVLi7TRAzywvVZljMNf/9J0O8z0YpsL4S6 043Q== X-Gm-Message-State: AGi0PuY7VoZv4Nnlv4mspznGrvvZGvjUiO72d+P1KQaz0cqyb/kegcON j8ZBxbymEvoyRHzgr21QIAZdPCMKNmb2VocmTRHxwg== X-Google-Smtp-Source: APiQypIJ0YJj7wDewOarzjPeBQ3TNEub+wV/hHY5m6cBUXRi3KnpEPdtdC0Na5tcpHRu2xgsP4ryTzs9hvl+w1CgaIA= X-Received: by 2002:a1f:1e11:: with SMTP id e17mr11345906vke.73.1587820693983; Sat, 25 Apr 2020 06:18:13 -0700 (PDT) MIME-Version: 1.0 References: <20200425131112.6E54F18C0B6@mercury.lcs.mit.edu> In-Reply-To: <20200425131112.6E54F18C0B6@mercury.lcs.mit.edu> From: Rob Pike Date: Sat, 25 Apr 2020 23:18:02 +1000 Message-ID: To: Noel Chiappa Content-Type: multipart/alternative; boundary="0000000000006e9a5805a41d502d" Subject: Re: [TUHS] v7 K&R C X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: The Eunuchs Hysterical Society Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --0000000000006e9a5805a41d502d Content-Type: text/plain; charset="UTF-8" To make chaining of calls simpler. Write f()->g()->h()->i() the other way and you'll see why Bjarne asked for the shorthand. -rob On Sat, Apr 25, 2020 at 11:12 PM Noel Chiappa wrote: > > From: Rob Pike > > > Convenient though the shorthand may be, it always bothered me as > > inconsistent and misleading. > > As someone who made very extensive use of procedure pointers (most notably > in > upcalls, which never caught on, alas), I couldn't agree more. > > Two very different things are happenging, but with the shorthand notation, > they share an identical representation. And for what? To save three > characters? > > Noel > > --0000000000006e9a5805a41d502d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
To make chaining of calls simpler. Write

f()->g()->h()->i()

the other way and yo= u'll see why Bjarne asked for the shorthand.

<= div>-rob


On Sat, Apr 25, 2020 at 11:12 PM Noel Ch= iappa <jnc@mercury.lcs.mit.ed= u> wrote:
=C2=A0 =C2=A0 > From: Rob Pike

=C2=A0 =C2=A0 > Convenient though the shorthand may be, it always bother= ed me as
=C2=A0 =C2=A0 > inconsistent and misleading.

As someone who made very extensive use of procedure pointers (most notably = in
upcalls, which never caught on, alas), I couldn't agree more.

Two very different things are happenging, but with the shorthand notation,<= br> they share an identical representation. And for what? To save three charact= ers?

=C2=A0 =C2=A0 =C2=A0Noel

--0000000000006e9a5805a41d502d--