Re: JSON Function Bike Shedding - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: JSON Function Bike Shedding
Date
Msg-id CAFj8pRA2W+2Aa0FGtdk_xvJiBq9zQxQr0faY_LfXT2DhS60rjw@mail.gmail.com
Whole thread Raw
In response to Re: JSON Function Bike Shedding  ("Petr Jelinek" <pjmodos@pjmodos.net>)
List pgsql-hackers
2013/2/19 Petr Jelinek <pjmodos@pjmodos.net>:
>> -----Original Message-----
>> From: pgsql-hackers-owner@postgresql.org [mailto:pgsql-hackers-
>> owner@postgresql.org] On Behalf Of Robert Haas
>> Sent: 19 February 2013 15:05
>> To: Merlin Moncure
>> Cc: David E. Wheeler; PostgreSQL-development Hackers
>> > The argument for removing json_ prefix is that when function behaviors
>> > are unambiguously controlled by the arguments, decorating the function
>> > name to match the input argument is unnecessary verbosity.
>>
>> I've come to value greppability of source code pretty highly.  I think
> that
>> some of the points you raise are valid, but in my (minority) opinion
>> overloading creates more problems than it solves.  You're not going to
>> convince me that get() is *ever* a good name for a function - you might as
>> well call it thing() or foo() for all the useful information that name
> conveys.
>
> Let me join the minority here, +1

me too +1

Pavel

>
> Regards
> Petr Jelinek
>
>
>
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [RFC] indirect toast tuple support
Next
From: Nicolas Barbier
Date:
Subject: Re: Materialized views WIP patch