From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id CV5+FEQK0WSqSzoAWB0awg (envelope-from ) for ; Mon, 07 Aug 2023 11:14:12 -0400 Authentication-Results: simark.ca; dkim=pass (2048-bit key; unprotected) header.d=lists.lttng.org header.i=@lists.lttng.org header.a=rsa-sha256 header.s=default header.b=SgnYXele; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 462461E0BB; Mon, 7 Aug 2023 11:14:12 -0400 (EDT) Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 926541E028 for ; Mon, 7 Aug 2023 11:14:09 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1691421249; bh=urW+q2bWFsVSYW2mkjwn10qHhBEKDaNTFQbco9Gak8o=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=SgnYXelexOzDqYgGTDi531yA6ZQ/uceY1m9eD2MuLy8Jh3d1azplCP9zV+2yNk2Dn feG3Z4Yo46qOrCNx/+0wSFYzlzal0pdslKXrpHiUvWYSrGS5BwhxLkfKgCs2nSxxUl fA1Uqs5Le9p+CGAPIIp4P6Wr0A6vaYAqiRZ/hLw6hG5oDVcmxebwlw13JOHOLCymJJ x197PTH/tmrQuzls/0gPB2Z3GLTVqDR+hzaH60ZPvxf3e9T4C3VjW55lMs1LlAtMi1 LI44DFaamzPpDZxAMSTLaF00Fze5M43t5NRo2H1pM32HMSOJDGag8ef0urF83c4+qy SL0e4rgpKSxLA== Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4RKKbh7498z2Jnr; Mon, 7 Aug 2023 11:14:08 -0400 (EDT) Received: from mail-4022.proton.ch (mail-4022.proton.ch [185.70.40.22]) by lists.lttng.org (Postfix) with ESMTPS id 4RJ9w205r0z2Hyh for ; Sat, 5 Aug 2023 14:24:17 -0400 (EDT) Date: Sat, 05 Aug 2023 18:24:10 +0000 To: "lttng-dev@lists.lttng.org" Message-ID: Feedback-ID: 62574427:user:proton MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 07 Aug 2023 11:14:08 -0400 Subject: [lttng-dev] [barectf] why YAML instead of CTF? X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: strager via lttng-dev Reply-To: strager Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" 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