From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.182.111.170 with SMTP id ij10mr3146836obb.42.1462312430132;
        Tue, 03 May 2016 14:53:50 -0700 (PDT)
X-Received: by 10.157.8.54 with SMTP id 51mr73014oty.13.1462312430074; Tue, 03
 May 2016 14:53:50 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!i5no2724341ige.0!news-out.google.com!uv8ni295igb.0!nntp.google.com!sq19no2170998igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 3 May 2016 14:53:49 -0700 (PDT)
In-Reply-To: <45cb9b19-b470-4649-843a-7b9f88411e6e@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=93.37.233.216;
 posting-account=9fwclgkAAAD6oQ5usUYhee1l39geVY99
NNTP-Posting-Host: 93.37.233.216
References: <45cb9b19-b470-4649-843a-7b9f88411e6e@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <77b74337-9dd2-4918-aab6-69e4b0b7935e@googlegroups.com>
Subject: Re: A suggestion about interfacing with C
From: mockturtle <framefritti@gmail.com>
Injection-Date: Tue, 03 May 2016 21:53:50 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Xref: news.eternal-september.org comp.lang.ada:30343
Date: 2016-05-03T14:53:49-07:00
List-Id: <comp.lang.ada>

Thank you everyone for your replies.

In the end, I decided to go for the "token" approach (suggested by Maciej) =
that I already used in some other case.  The reason to use this approach is=
 that the "send" functions of the library require the message header and pa=
yload to be stored inside a special struct, whose definition is unknown (at=
 least, very difficult to find :-) and that the user manipulates using some=
 library functions.  It turns out that it is simpler to build the payload o=
n the Ada side, then convert it to a "C string" that is moved to the C side=
 where the final assembling -- before transmission -- is done.

Thank you again.

Riccardo