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

From Petr Jelinek
Subject Re: JSON Function Bike Shedding
Date
Msg-id 000601ce0eab$114fec10$33efc430$@pjmodos.net
Whole thread Raw
In response to Re: JSON Function Bike Shedding  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: JSON Function Bike Shedding  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: JSON Function Bike Shedding  ("David E. Wheeler" <david@justatheory.com>)
Re: JSON Function Bike Shedding  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
> -----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

Regards
Petr Jelinek





pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: JSON Function Bike Shedding
Next
From: Robert Haas
Date:
Subject: Re: [RFC] indirect toast tuple support