Re: Calling PL functions with named parameters - Mailing list pgsql-hackers

From Oliver Jowett
Subject Re: Calling PL functions with named parameters
Date
Msg-id 411DFD0A.20409@opencloud.com
Whole thread Raw
In response to Re: Calling PL functions with named parameters  (Gaetano Mendola <mendola@bigfoot.com>)
Responses Re: Calling PL functions with named parameters  (Gaetano Mendola <mendola@bigfoot.com>)
List pgsql-hackers
Gaetano Mendola wrote:
> Oliver Jowett wrote:
> 
>> Gaetano Mendola wrote:
>>
>>> Oliver Jowett wrote:
>>>
>>>> David Fetter wrote:
>>>>
>>>>> Dennis has pointed out that mixing the call-with-named-parameter
>>>>> interface with call-by-order-of-parameters one would cause confusion,
>>>>
>>>>
>>>>
>>>> Python's equivalent syntax allows you to mix the two forms so long 
>>>> as all the by-position parameters come first:
>>>>
>>> python don't have overloaded functions...
>>
>> It doesn't change how you'd handle overloaded functions; you still 
>> have a type for every parameter available.
> 
> 
> I think will be a mess that will break the "minor surprise" principle,
> even the bad C++ stays away from this field ( se explicit constructors,
> and automatic cast limited to only one level ).

I don't understand your argument. What is the surprising behaviour you 
are worried about?

-O


pgsql-hackers by date:

Previous
From: Oliver Jowett
Date:
Subject: Re: Calling PL functions with named parameters
Next
From: "Simon@2ndquadrant.com"
Date:
Subject: Re: will PITR in 8.0 be usable for "hot spare"/"log shipping" type of replication