Re: Ryu floating point output patch

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Ryu floating point output patch
Date: 2018-12-14 18:01:19
Message-ID: 87k1kcyp3l.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Thomas" == Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:

>>> Do we have any reason for the restriction beyond stylistic preference?

>> No. Robert and Tom were against allowing mixing declarations and
>> code, a few more against // comments. I don't quite agree with
>> either, but getting to the rest of C99 seemed more important than
>> fighting those out at that moment.

Thomas> -1 for making superficial changes to code that we are
Thomas> "vendoring", unless it is known to be dead/abandoned and we're
Thomas> definitively forking it. It just makes it harder to track
Thomas> upstream's bug fixes and improvements, surely?

Well, the question there is how far to take that principle; do we avoid
pgindent'ing the code, do we avoid changing uint64_t etc. to uint64
etc., and so on.

(I notice that a stray uint8_t that I left behind broke the Windows
build but not the linux/bsd one, so something would have to be fixed in
the windows build in order to avoid having to change that.)

The Ryu code is perhaps an extreme example because it follows almost the
exact reverse of our coding standard.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-12-14 18:16:30 Re: removal of dangling temp tables
Previous Message Tom Lane 2018-12-14 17:57:23 Re: removal of dangling temp tables