OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: annotation question - 14.2.2 Target


Hello,

 

Hopefully a quick question. Section 14.2.2 Target

States the following.

 

·         qualified name of an action followed by parentheses containing the binding parameter type of a bound action overload to identify that bound overload, or by empty parentheses to identify the unbound overload

·         qualified name of a function followed by parentheses containing the comma-separated list of the parameter types of a bound or unbound function overload in the order of their definition in the function overload

 

And there seems to be a key difference in how the target path of an bound action is handled vs that of a bound function.
In a function’s target path it seems all parameter types are specified whereas for an action it is “only” the binding parameter type  

 

Is it true that

  • actions allow overloads and they need to be uniquely resolvable by the binding parameter type
  • functions allows overloads and they need to be uniquely resolvable by the combination of all parameters type’s

 

12.2 and 12.4 seem to say that but don’t make it very explicit that actions and functions are defined differently in that regard.

 

Christof



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]