projects
/
ctf.git
/ blobdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
enum: Clarify behavior for omitted values after range
[ctf.git]
/
common-trace-format-specification.txt
diff --git
a/common-trace-format-specification.txt
b/common-trace-format-specification.txt
index a8ed0245d44db2701819c0816c8afbad5e901752..e0944b5d84b6491e33c6e9c0b6b889b0751b845b 100644
(file)
--- a/
common-trace-format-specification.txt
+++ b/
common-trace-format-specification.txt
@@
-1,4
+1,4
@@
-Common Trace Format (CTF) Specification (v1.8)
+Common Trace Format (CTF) Specification (v1.8
.1
)
Mathieu Desnoyers, EfficiOS Inc.
Mathieu Desnoyers, EfficiOS Inc.
@@
-358,7
+358,8
@@
enum name : integer_type {
};
If the values are omitted, the enumeration starts at 0 and increment of 1 for
};
If the values are omitted, the enumeration starts at 0 and increment of 1 for
-each entry:
+each entry. An entry with omitted value that follows a range entry takes
+as value the end_value of the previous range + 1:
enum name : unsigned int {
ZERO,
enum name : unsigned int {
ZERO,
This page took
0.023809 seconds
and
4
git commands to generate.