[OASIS Issue Tracker] Commented: (ODATA-313) Problem with "Function Overload Resolution" due to null values having ambiguous type

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32882#action_32882 ] 

Ralf Handl commented on ODATA-313:
----------------------------------

I think we don't need to worry about this disambiguity: if a service designer uses the same function name and the same parameter name for "compatible" types with a different meaning, then the service is seriously problematic:

GET ~/Question(Answer=42) should produce the same result for a "unsigned short forty-two" and a "64-bit forty-two".

So in my opinion the current suffixes are sufficient, and its the service designer's job to avoid ambiguities in the function overload (s)he creates.

Btw: 'INF' is not ambiguous: it's a string. INF (without the quotes) is positive infinity, and as a mathematician I see no difference between "single infinity" and "double infinity".

PS: I DID propose to clean up the numeric types in ODATA-256 :-)

> Problem with "Function Overload Resolution" due to null values having ambiguous type
> ------------------------------------------------------------------------------------
>
>                 Key: ODATA-313
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-313
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol , OData URL Conventions 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Evan Ireland
>            Assignee: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> CSDL spec (2013-03-12) states in section 10.5.3.4 "Function overload resolution"
>   Functions overloads are supported in OData, meaning a service MAY expose multiple functions with the same name that take a different set of parameters.
>   When a function is invoked (using any of the three parameter syntaxes) the parameter names and parameter values are specified in the URL, and the parameter types can be deduced from each parameter value. The combination of the Function name and the unordered list of parameter types and names is always sufficient to identify a particular function overload.
> However, if one or more parameter values are null, there might be multiple functions (with same-named parameters but differing types corresponding to the null-valued parameter(s)). A null value can resolve to any primitive/complex/entity type. Thus overload resolution would be ambiguous.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira