From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79385 invoked by alias); 2 May 2019 15:07:41 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 79296 invoked by uid 89); 2 May 2019 15:07:41 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.9 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 02 May 2019 15:07:40 +0000 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F094B3086273; Thu, 2 May 2019 15:07:38 +0000 (UTC) Received: from [10.36.116.145] (ovpn-116-145.ams2.redhat.com [10.36.116.145]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 740C61834B; Thu, 2 May 2019 15:07:38 +0000 (UTC) To: Nick Alcock , binutils@sourceware.org References: <20190430225706.159422-1-nick.alcock@oracle.com> <20190430225706.159422-3-nick.alcock@oracle.com> From: Nick Clifton Openpgp: preference=signencrypt Subject: Re: [PATCH 02/19] include: new header ctf-api.h Message-ID: <863e1bbe-c59f-5256-ed33-01f38af717f0@redhat.com> Date: Thu, 02 May 2019 15:07:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <20190430225706.159422-3-nick.alcock@oracle.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2019-05/txt/msg00099.txt.bz2 Hi Nick, > This non-installed header is the means by which libctf consumers > communicate with libctf. By "non-installed" do you mean that it would not be placed into /usr/include ? If so, then how do consumers know how to communicate with libctf, given that they might be compiled without access to the ctf sources ? > +/* Clients can open one or more CTF containers and obtain a pointer to an > + opaque ctf_file_t. Types are identified by an opaque ctf_id_t token. > + They can also open or create read-only archives of CTF containers in a > + ctf_archive_t. Are CTF archives just arbitrary collections of CTF containers or is there more to them than that ? Cheers Nick