> On 30 Nov 2018, at 19:50, phil--- via Pharo-users > <pharo-users@lists.pharo.org> wrote: > > > From: "p...@highoctane.be" <p...@highoctane.be> > Subject: Re: [Pharo-users] UFFI and opaque(ish) types > Date: 30 November 2018 at 19:50:03 CET > To: Any question about pharo is welcome <pharo-users@lists.pharo.org> > > > Inherit from FFIOpaqueObject > > + initialize TypeMap > > I have a few here: > > https://github.com/Pharophile/XmppTalk > <https://github.com/Pharophile/XmppTalk> > > https://github.com/Pharophile/XmppTalk/tree/master/packages/XmppTalk-ExternalStructures.package > > <https://github.com/Pharophile/XmppTalk/tree/master/packages/XmppTalk-ExternalStructures.package> > https://github.com/Pharophile/XmppTalk/blob/master/packages/XmppTalk-LibStrophe.package/StropheLib.class/class/initializeTypeMap.st > > <https://github.com/Pharophile/XmppTalk/blob/master/packages/XmppTalk-LibStrophe.package/StropheLib.class/class/initializeTypeMap.st> > > HTH > Phil
Yes, as he says/shows :) Esteban > > > > On Fri, Nov 30, 2018 at 2:39 PM Alistair Grant <akgrant0...@gmail.com > <mailto:akgrant0...@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 > > > >
