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] Issue Comment Edited: (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=32999#action_32999 ] 

Stefan Drees edited comment on ODATA-341 at 4/12/13 12:06 PM:
--------------------------------------------------------------

Is there a typo where more should read mere in: "[...]whereas all the other integer types simply allow for more digits to be returned[...]"?

Two things from the ABNF:

1. Let's all remeber again, the case insensitive nature of ABNF (i.e. outside the single quote resevates of our extended usage):

int64 = int64Body [ "L" ] 
int64Body = [ sign ] 1*19DIGIT ; numbers in the range from -9223372036854775808 to 9223372036854775807

the two lines cited from current ABNF (svn revision 231) have a double quote enclosed L which may well be a lowercase letter l.

2. And also, that this postfix letter (L or l) as it is placed inside square brackets is thus optional.

      was (Author: sdrees):
    Is there a typo where more should read mere in: "[...]whereas all the other integer types simply allow for more digits to be returned[...]"?

Oh, an beware of the case insensitive nature of ABNF outside the single quote resevates of our extended usage:

int64 = int64Body [ "L" ] 
int64Body = [ sign ] 1*19DIGIT ; numbers in the range from -9223372036854775808 to 9223372036854775807

the two lines cited from current ABNF (svn revision 231) have a double quote enclosed L which may well be a lowercase letter l.

And also, that this postfix letter (L or l) is placed inside square brackets thus optional.
  
> 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]