<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Wow, this is incroyable.<br><br><div dir="ltr"><span style="font-size: 13pt;">/—————————————————————/</span><div><span style="font-size: 13pt;">For encrypted mail use jgpfersich@protonmail.com - Free</span><span style="font-size: 13pt;"> account at ProtonMail.com</span><div>Web: https://objectnets.net and https://objectnets.org</div></div><div>https://datascilv.com https://datascilv.org</div><div><br></div></div><div dir="ltr"><br><blockquote type="cite">On May 18, 2020, at 12:56, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>Hi all,</div><div>I started to write a documentation of FFI implementation two or three months ago, I don't remember exactly, it's an eternity. The lock down did not give me an opportunity to continue. I want to publish with some liberal CC license, but I don't have chosen a support format yet. On one side, I wanted to focus on contents more than on the format. But on the other side, I want some graphical illustrations accurate enough. I wrote in Word because it was easy for me to include tables and graphics, but it's kinda stupid, especially because Word make you focus on format more than contents ! LaTeX is not general enough, it would rather be a backend nowadays. I contemplated using pandoc which has good support, or the much more limited Pilar, which at least is Smalltalk based...</div><div>The structure is not well established and the work is very preliminary, but since there is some demand, I give a pdf copy here as is, I hope it's not too big for the list. This probably should better be continued as a collaborative work anyway.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le lun. 18 mai 2020 à 21:33, Levente Uzonyi <<a href="mailto:leves@caesar.elte.hu">leves@caesar.elte.hu</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">How does UFFI come here? AFAIK it's nothing but a different image-side <br>
code using the VM's FFI implementation along with the signature notion <br>
Igor used in NativeBoost (which is great btw because it's "as you would <br>
write it in C" and doesn't require language changes).<br>
<br>
<br>
Levente<br>
<br>
On Mon, 18 May 2020, Jakob Reschke wrote:<br>
<br>
> Do we even have UFFI in Squeak? This was the thing I meant is missing to reuse Pharo's libgit2 bindings, in the vm-dev thread. <br>
> <br>
> Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" target="_blank">marcel.taeumel@hpi.de</a>> schrieb am Mo., 18. Mai 2020, 20:07:<br>
> Hi Vanessa,<br>
> > I don't have the code in front of me but there is the parser you could check ;)<br>
> <br>
> I tried. I suspect that the generator cannot do it but I have to wrap it manually. But I am not sure. Reverse engineering UnifiedFFI did not help yet either. Have to put more time into it. :-)<br>
> <br>
> Best,<br>
> Marcel<br>
><br>
> Am 18.05.2020 20:00:16 schrieb Vanessa Freudenberg <<a href="mailto:vanessa@codefrau.net" target="_blank">vanessa@codefrau.net</a>>:<br>
><br>
> On Mon, May 18, 2020 at 7:05 AM Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" target="_blank">marcel.taeumel@hpi.de</a>> wrote:<br>
> Hi, there!<br>
> <br>
> In the #fields method of a new ExternalStructure, how can I express a pointer to another external structure?<br>
> <br>
> First, non-pointer works as expected:<br>
> ^ #( (other MyStruct) )<br>
> <br>
> Second, this just treats it as a void*, which returns a generic ExternalData:<br>
> ^ #( (other 'MyStruct*') )<br>
> <br>
> Third, this gives me a debugger:<br>
> ^ #( (other MyStruct *) )<br>
> <br>
> <br>
> I don't have the code in front of me but there is the parser you could check ;)<br>
> <br>
> It might be *MyStruct.<br>
> <br>
> - Vanessa - <br>
> <br>
> <br>
> <br>
><br>
</blockquote></div>
<div><The Squeak Foreign Function Interface and its implementation demystified.pdf></div><span></span><br></div></blockquote></body></html>