Return-Path: DKIM-Filter: OpenDKIM Filter v2.10.3 mail.efficios.com A51D2292F49 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=efficios.com; s=default; t=1588162084; bh=C7hVyDdfrSaGa2gwW8r57mngtuCRDKJqwuJiSNOBgCo=; h=Date:From:To:Message-ID:MIME-Version; b=ipNyF8hsZ9oPZAwy6KWF+zxc6Ax2OAtFwAUVs1rnjpoEP81Vm0ouYheSwkoCtzdnE JCxtdbCXMO5uVyJtOTkpbpFr226lhyBF2YmlSuGWK13rzoZVttbyn4Poseo/TIXczb XQhEYnXr6hq2va11c04hMa8RhUwWiA4H3s5le2lFdglMi1ll7chGIlUCK1QJ+krNNl 5Uo/QztpeOJNzrJvoBqt6L+6VxEchraRaskgTdoXyW7jXFzwaI/2XCuYwst2N3nrXV 7sOHOiMONW+Di+Vrwk2j/GYrUctTefJjzEW0wJm3O3FgObCizlrR15RorMgodNLs/E EnQTC7w3bShUg== Date: Wed, 29 Apr 2020 08:08:04 -0400 (EDT) From: Mathieu Desnoyers Message-ID: <104691146.75724.1588162084473.JavaMail.zimbra@efficios.com> In-Reply-To: <1859708486.72922.1588099890391.JavaMail.zimbra@efficios.com> References: <20200423205226.496-1-mathieu.desnoyers@efficios.com> <20200423205226.496-2-mathieu.desnoyers@efficios.com> <1031751564.72894.1588099218629.JavaMail.zimbra@efficios.com> <1859708486.72922.1588099890391.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [diamon-discuss] [RFC PATCH CTF 1/3] Clarify that unlisted enum values are implementation-defined List-Id: DiaMon diagnostic and monitoring workgroup general discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Proulx Cc: Diamon discuss , lttng-dev , Jeremie Galarneau , Genevieve Bastien ----- On Apr 28, 2020, at 2:51 PM, Mathieu Desnoyers mathieu.desnoyers@effi= cios.com wrote: > ----- On Apr 28, 2020, at 2:40 PM, Philippe Proulx pproulx@efficios.com w= rote: >=20 >> ----- Original Message ----- >>> From: "Mathieu Desnoyers" >>> To: "gbastien+lttng" , "Matthew Khouzam" >>> , >>> diamon-discuss@linuxfoundation.org, pproulx@efficios.com, "Jeremie Gala= rneau" >>> >>> Cc: "lttng-dev" , "Mathieu Desnoyers" >>> >>> Sent: Thursday, 23 April, 2020 16:52:24 >>> Subject: [RFC PATCH CTF 1/3] Clarify that unlisted enum values are >>> implementation-defined >>=20 >>> From: Genevi=C3=A8ve Bastien >>>=20 >>> Signed-off-by: Genevi=C3=A8ve Bastien >>> Signed-off-by: Mathieu Desnoyers >>> --- >>> common-trace-format-specification.md | 3 +++ >>> 1 file changed, 3 insertions(+) >>>=20 >>> diff --git a/common-trace-format-specification.md >>> b/common-trace-format-specification.md >>> index fd49e59..f5fea51 100644 >>> --- a/common-trace-format-specification.md >>> +++ b/common-trace-format-specification.md >>> @@ -464,6 +464,9 @@ enum { >>> } >>> ~~~ >>>=20 >>> +The mappings in the enumeration type do not have to be exhaustive. >>> +Unlisted values are implementation defined. >>> + >>=20 >> Why not just: >>=20 >> An enumeration field can have an integral value which its type does n= ot >> map to a string. >>=20 >> ? >=20 > Good point, I will use that wording. Genevi=C3=A8ve pointed out on IRC that the sentence above is weird. Would t= he following convey the right meaning ? "An enumeration field can have an integral value for which the associated e= numeration type does not map to a string." Thanks, Mathieu >=20 > Thanks, >=20 > Mathieu >=20 >>=20 >> Phil >>=20 >>> ### 4.2 Compound types >>>=20 >>> Compound are aggregation of type declarations. Compound types include >>> -- >> > 2.11.0 >=20 > -- > Mathieu Desnoyers > EfficiOS Inc. > http://www.efficios.com --=20 Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com