From: RADERMACHER Ansgar via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] [barectf] no nested types?
Date: Fri, 5 Feb 2021 21:58:25 +0000 [thread overview]
Message-ID: <386C5D4D5C53C24CBC2C60CAAFD2136A5B4A9BAB@EXDAG0-B1.intra.cea.fr> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]
Hello,
I've generated a config.yaml from type definitions in UML. If the type of a payload field is a UML DataType, the generator produces an associated type alias file with "class = structure" and the contained members.
When I tried to compile the configuration file, I get an error message from barectf:
`field-type` property: Nested structure field types are not supported
It this really not supported or are there other mechanisms that enable the use of nested types? If not supported, it would be an important restriction which seems to be not prominently documented (in [1], there is a parenthesis "except a structure field type object" but it's easy to miss)
Best regards
Ansgar
[1] https://barectf.org/docs/barectf/3.0/yaml/struct-ft-obj.html
[-- Attachment #1.2: Type: text/html, Size: 2358 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2021-02-05 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 21:58 RADERMACHER Ansgar via lttng-dev [this message]
2021-02-08 10:27 ` [lttng-dev] [barectf] no nested types? RADERMACHER Ansgar via lttng-dev
2021-02-08 14:58 ` Philippe Proulx via lttng-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=386C5D4D5C53C24CBC2C60CAAFD2136A5B4A9BAB@EXDAG0-B1.intra.cea.fr \
--to=lttng-dev@lists.lttng.org \
--cc=Ansgar.RADERMACHER@cea.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).