From: | "Petr Jelinek" <pjmodos(at)pjmodos(dot)net> |
---|---|
To: | "'Robert Haas'" <robertmhaas(at)gmail(dot)com>, "'Merlin Moncure'" <mmoncure(at)gmail(dot)com> |
Cc: | "'David E(dot) Wheeler'" <david(at)justatheory(dot)com>, "'PostgreSQL-development Hackers'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: JSON Function Bike Shedding |
Date: | 2013-02-19 14:11:53 |
Message-ID: | 000601ce0eab$114fec10$33efc430$@pjmodos.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org [mailto:pgsql-hackers-
> owner(at)postgresql(dot)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
Regards
Petr Jelinek
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-02-19 14:12:02 | Re: [RFC] indirect toast tuple support |
Previous Message | Robert Haas | 2013-02-19 14:04:34 | Re: JSON Function Bike Shedding |