Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dq1wx-0003Xz-9M for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Sep 2017 18:54:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dq1ww-0006VD-BO for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Sep 2017 18:54:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dq1vP-0003jx-MA for pgsql-hackers@postgresql.org; Thu, 07 Sep 2017 18:53:15 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dq1vD-0005U8-LT for pgsql-hackers@postgresql.org; Thu, 07 Sep 2017 18:53:15 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id v87Ir0DO004153; Thu, 7 Sep 2017 14:53:00 -0400 From: Tom Lane To: Peter Eisentraut cc: Michael Paquier , pgsql-hackers Subject: Re: assorted code cleanup In-reply-to: <98ba2e15-250b-8bce-fa4c-777e0d76cd4e@2ndquadrant.com> References: <2beab0ef-69f9-dab3-cacd-8fdf417bca96@2ndquadrant.com> <11524.1504639947@sss.pgh.pa.us> <98ba2e15-250b-8bce-fa4c-777e0d76cd4e@2ndquadrant.com> Comments: In-reply-to Peter Eisentraut message dated "Thu, 07 Sep 2017 14:00:18 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4151.1504810380.1@sss.pgh.pa.us> Date: Thu, 07 Sep 2017 14:53:00 -0400 Message-ID: <4152.1504810380@sss.pgh.pa.us> List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Peter Eisentraut writes: > On 9/5/17 15:32, Tom Lane wrote: >> I do agree with the idea that we should use the * notation in cases where >> the reader might otherwise think that a plain function was being invoked, >> ie I don't like >> some_function_pointer(args); >> Even if the compiler isn't confused, readers might be. But in the case of >> structname->pointerfield(args); >> it's impossible to read that as a plain function call, so I'm okay with >> dropping the extra punctuation there. > Committed that way. Thanks. Is it worth memorializing this in the docs somewhere, perhaps "53.4. Miscellaneous Coding Conventions" ? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers