[OASIS Issue Tracker] (ODATA-919) Specify the result type for each operation based on operator types

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

    [ https://issues.oasis-open.org/browse/ODATA-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63073#comment-63073 ] 

Evan Ireland commented on ODATA-919:
------------------------------------

For "a)", it may result in a difficulty with target languages (pretty much all of them) that don't permit Infinity to be represented with an integral type.

Why does "b)" say "promotion rules will promote, then type " rather than "roperand" as we see in "d)"?

For "c)", note that Int16(-32768) / Int16(-1) gives 32768, which cannot be represented as an Int16. Will service implementors take this into account, or perhaps should we just require Int64 result as in "a)".

Simplification might come from "int* add/mul/sub/mod int* => Int64".



> Specify the result type for each operation based on operator types
> ------------------------------------------------------------------
>
>                 Key: ODATA-919
>                 URL: https://issues.oasis-open.org/browse/ODATA-919
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions
>    Affects Versions: V4.0_OS
>         Environment: Proposed
>            Reporter: Martin Zurmuehl
>            Assignee: Evan Ireland
>             Fix For: V4.01_WD01
>
>
> See ODATA-785 for a description of the issue --> Comments Section.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)