json: Update references to RFC 7159 to RFC 8259
RFC 8259 (December 2017) obsoletes RFC 7159 (March 2014). Signed-off-by: Markus Armbruster <armbru@redhat.com> Message-Id: <20180823164025.12553-59-armbru@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
parent
8bca4613e6
commit
37aded92c2
@ -25,7 +25,7 @@ typedef enum {
|
||||
|
||||
/*
|
||||
* QNum encapsulates how our dialect of JSON fills in the blanks left
|
||||
* by the JSON specification (RFC 7159) regarding numbers.
|
||||
* by the JSON specification (RFC 8259) regarding numbers.
|
||||
*
|
||||
* Conceptually, we treat number as an abstract type with three
|
||||
* concrete subtypes: floating-point, signed integer, unsigned
|
||||
|
@ -120,7 +120,7 @@
|
||||
##
|
||||
# @JSONType:
|
||||
#
|
||||
# The four primitive and two structured types according to RFC 7159
|
||||
# The four primitive and two structured types according to RFC 8259
|
||||
# section 1, plus 'int' (split off 'number'), plus the obvious top
|
||||
# type 'value'.
|
||||
#
|
||||
|
@ -516,7 +516,7 @@ static QObject *parse_literal(JSONParserContext *ctxt)
|
||||
}
|
||||
case JSON_FLOAT:
|
||||
/* FIXME dependent on locale; a pervasive issue in QEMU */
|
||||
/* FIXME our lexer matches RFC 7159 in forbidding Inf or NaN,
|
||||
/* FIXME our lexer matches RFC 8259 in forbidding Inf or NaN,
|
||||
* but those might be useful extensions beyond JSON */
|
||||
return QOBJECT(qnum_from_double(strtod(token->str, NULL)));
|
||||
default:
|
||||
|
Loading…
Reference in New Issue
Block a user