aboutsummaryrefslogtreecommitdiff
path: root/include/qapi
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2015-11-18 01:52:52 -0700
committerMarkus Armbruster <armbru@redhat.com>2015-12-17 08:21:27 +0100
commitc43567c12042cf401b039bfc94a5f85e1cc1e796 (patch)
treef73be2b1a06d27493f5350f56e546b95338ccd71 /include/qapi
parent27b60ab93bd1d5d8c85f009aac7a97ffd2c53c86 (diff)
downloadqemu-c43567c12042cf401b039bfc94a5f85e1cc1e796.zip
qemu-c43567c12042cf401b039bfc94a5f85e1cc1e796.tar.gz
qemu-c43567c12042cf401b039bfc94a5f85e1cc1e796.tar.bz2
qapi: Fix c_name() munging
The method c_name() is supposed to do two different actions: munge '-' into '_', and add a 'q_' prefix to ticklish names. But it did these steps out of order, making it possible to submit input that is not ticklish until after munging, where the output then lacked the desired prefix. The failure is exposed easily if you have a compiler that recognizes C11 keywords, and try to name a member '_Thread-local', as it would result in trying to compile the declaration 'uint64_t _Thread_local;' which is not valid. However, this name violates our conventions (ultimately, want to enforce that no qapi names start with single underscore), so the test is slightly weaker by instead testing 'wchar-t'; the declaration 'uint64_t wchar_t;' is valid in C (where wchar_t is only a typedef) but would fail with a C++ compiler (where it is a keyword). Fix things by reversing the order of actions within c_name(). Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <1447836791-369-18-git-send-email-eblake@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'include/qapi')
0 files changed, 0 insertions, 0 deletions