Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: strager via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] [barectf] why YAML instead of CTF?
Date: Sat, 05 Aug 2023 18:24:10 +0000	[thread overview]
Message-ID: <tFicevizpfz9CtNCCV6nl0_0SGJOSKJwbWV2s4XvDMWHogGJvJe4yrgcIndnifk0doSMNuVlONo0S5z_yrIWmh8TjxX2hs_RykJRZcOCIKQ=@strager.net> (raw)

I have a CTF metadata file (schema) and hand-written parsers and writers for streams with that schema. I am interested in writing a tool which generates the parsers and writers (instead of hand-writing them).

It looks like barectf is similar to the tool I want to build. However, barectf reads a custom file format for the schema instead of reading a CTF metadata file.

Question: Why does barectf read a custom YAML format instead of reading CTF metadata? My plan was for my tool to read the schema from a CTF metadata file. Are there technical reasons why it's bad to make a code generator with CTF metadata as input? Because babeltrace2 can read CTF metadata files, I thought CTF metadata was machine-readable.

Thanks,
strager

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

                 reply	other threads:[~2023-08-07 15:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='tFicevizpfz9CtNCCV6nl0_0SGJOSKJwbWV2s4XvDMWHogGJvJe4yrgcIndnifk0doSMNuVlONo0S5z_yrIWmh8TjxX2hs_RykJRZcOCIKQ=@strager.net' \
    --to=lttng-dev@lists.lttng.org \
    --cc=s@strager.net \
    /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