On 30 Nov 2018, at 19:50, phil--- via Pharo-users <pharo-users@lists.pharo.org> wrote:From: "phil@highoctane.be" <phil@highoctane.be>Subject: Re: [Pharo-users] UFFI and opaque(ish) typesDate: 30 November 2018 at 19:50:03 CETTo: Any question about pharo is welcome <pharo-users@lists.pharo.org>Inherit from FFIOpaqueObject+ initialize TypeMapI have a few here:HTHPhil
On Fri, Nov 30, 2018 at 2:39 PM Alistair Grant <akgrant0710@gmail.com> wrote:How are opaque(ish) types normally handled in UFFI (or FFI)?
E.g. if I want to use libstuff which defines the following structure:
struct stuffstruct {
typeA a;
typeB b;
} stufftype;
I might know they're integers, but not the size, signed vs. unsigned,
etc.
The definitions of typeA and typeB are buried in multiple layers of
header files, dependent on #if tests, can be different sizes on
different platforms (e.g. Linux vs. MacOS), etc.?
Is this documented somewhere?
Thanks,
Alistair