[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-313) Problem with "Function Overload Resolution" due to null values having ambiguous type
[ http://tools.oasis-open.org/issues/browse/ODATA-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evan Ireland updated ODATA-313:
-------------------------------
Description:
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.
was:
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.
> 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
> Affects Versions: V4.0_WD01
> Reporter: Evan Ireland
>
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]