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: [OASIS Issue Tracker] Commented: (ODATA-341) Can we get rid of the trailing 'L' for int64 numbers

    [ http://tools.oasis-open.org/issues/browse/ODATA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33002#action_33002 ] 

Hubert Heijkers commented on ODATA-341:

Mmm, not sure how I've missed the fact the 'L' is optional. Leaves the question why anybody would add it. I suppose we can close this then with no further action.

> Can we get rid of the trailing '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
> According to the ABNF we need to append the capital 'L' character to an int64 integer whereas all the other integer types simply allow for more digits to be returned. Dear I ask why? 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 (and even with certain 15 digit numbers) an int64 number is required?

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]