[
https://issues.apache.org/jira/browse/QPID-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725466#comment-14725466
]
Gordon Sim commented on QPID-6718:
----------------------------------
Apart from stating that "numbers in the range of Java long are supported" the
JMS spec mostly defers to the Java language spec here: "Exact numeric literals
use the Java integer literal syntax." in 3.8.1.1 which is
https://docs.oracle.com/javase/specs/jls/se7/html/jls-3.html#jls-3.10.1 and
includes:
"A hexadecimal numeral consists of the leading ASCII characters 0x or 0X
followed by one or more ASCII hexadecimal digits interspersed with underscores,
and can represent a positive, zero, or negative integer. "
"An octal numeral consists of an ASCII digit 0 followed by one or more of the
ASCII digits 0 through 7 interspersed with underscores, and can represent a
positive, zero, or negative integer. "
and
"An integer literal is of type long if it is suffixed with an ASCII letter L or
l"
> parsing errors for integer literals in selectors
> ------------------------------------------------
>
> Key: QPID-6718
> URL: https://issues.apache.org/jira/browse/QPID-6718
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: qpid-cpp-0.34
> Reporter: Gordon Sim
> Assignee: Andrew Stitcher
> Priority: Minor
>
> There are a few integer literals that cause selector parsing to fail or the
> resulting evaluation to be incorrect:
> (a) hexadecimal literals don't seem to be recognised, e.g. 0xFF will result
> in a parse error
> (b) octal literals are evaluated as decimal e.g 077 is interpreted as decimal
> 77 rather than decimal 63
> (c) large numbers fail with a lexical cast error, e.g -9223372036854775808L
> or 9223372036854775807L
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
