From c6d7abc5412a0f3d9bcf21a1f53041411c7e9120 Mon Sep 17 00:00:00 2001 From: Mathieu Desnoyers Date: Wed, 19 Jan 2011 15:29:03 -0500 Subject: [PATCH] Add true/false explanation Signed-off-by: Mathieu Desnoyers --- common-trace-format-proposal.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/common-trace-format-proposal.txt b/common-trace-format-proposal.txt index 4da86e3..a69c0a3 100644 --- a/common-trace-format-proposal.txt +++ b/common-trace-format-proposal.txt @@ -771,7 +771,8 @@ and trace UUID. The metadata can be parsed by reading through the metadata strings, skipping newlines and null-characters. Type names are made of a single identifier, and can be surrounded by prefix/postfix. Text contained within "/*" and "*/", as -well as within "//" and end of line, are treated as comments. +well as within "//" and end of line, are treated as comments. Boolean values can +be represented as true, TRUE, or 1 for true, and false, FALSE, or 0 for false. The grammar representing the CTF metadata is presented in Appendix C. CTF Metadata Grammar. -- 2.34.1