| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JSON Function Bike Shedding |
| Date: | 2013-02-17 14:33:08 |
| Message-ID: | 5120EA24.5090209@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/16/2013 07:50 PM, David E. Wheeler wrote:
> On Feb 16, 2013, at 12:47 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>> To answer David's point, there is no point in having both
>>
>> get(json,text)
>> get(json, variadic text[])
>>
>> since the second can encompass the first, and having both would make calls ambiguous.
> Oh. Well then how about
>
> get(json, int)
> get(json, text)
> get(json, text[])
>
> ?
>
No, then we don't have a variadic version. You are going to have to
accept that we can't make one function name cover all of this.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2013-02-17 15:10:35 | Re: overlapping strncpy/memcpy errors via valgrind |
| Previous Message | Andres Freund | 2013-02-17 14:22:10 | overlapping strncpy/memcpy errors via valgrind |