[OASIS Issue Tracker] Updated: (ODATA-341) Can we get rid of the optional trailing 'L'/'l' for int64 numbers

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hubert Heijkers updated ODATA-341:
----------------------------------

    Proposal: Remove the optional trailing 'l'/'L', 'f'/'F', 'd'/'D' and 'm'/'M' qualifier for int64, single, double and decimal numbers respectively.  (was: Remove the optional trailing 'L'/'l' character for int64 numbers.)

> Can we get rid of the optional trailing 'L'/'l' for int64 numbers
> -----------------------------------------------------------------
>
>                 Key: ODATA-341
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-341
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules
>         Environment: [Proposed]
>            Reporter: Hubert Heijkers
>            Priority: Minor
>
> According to the ABNF an optional 'L'/'l' character MAY be included. I was asked why this was and failed to give an answer. Dear I ask why we allow this whereas we don't make any distinction that way for the other integer types?We already allow for upscaling to a bigger type, why couldn't any integer number be just specified using its digits full well knowing that if more then 15 digits are required it has to be an int64 number ?

-- 
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