[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-500) Require function/action overloads to differ by ordered set of parameter types
[ http://tools.oasis-open.org/issues/browse/ODATA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34729#action_34729 ] Michael Pizzo commented on ODATA-500: ------------------------------------- Treating type definitions as different types is a reasonable compromise. > Require function/action overloads to differ by ordered set of parameter types > ----------------------------------------------------------------------------- > > Key: ODATA-500 > URL: http://tools.oasis-open.org/issues/browse/ODATA-500 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: New Feature > Components: OData CSDL > Affects Versions: V4.0_CS01 > Environment: [Proposed][CS02] > Reporter: Michael Pizzo > Fix For: V4.0_CSD03 > > > [CSDL] does function overload resolution by the unordered set of parameter names. Most languages do function overload resolution according to the ordered set of parameter types. > Currently, [CSDL] allows two function overloads with different parameter names to have the same types: > <Function Name="Evaluate" ReturnType="Integer"> > <Parameter Name="Input" Type="Edm.Integer"/> > </Function> > <Function Name="Evaluate" ReturnType="Integer"> > <Parameter Name="Variable" Type="Edm.Integer"/> > </Function> > This doesn't add significant value, could be confusing, and would not be supported in most programming languages. > It is okay for OData to be more restrictive than conventional programming languages, but having it arbitrarily less restrictive makes it difficult to expose a client side programming model in a conventional language. -- 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]