From: Marc Ihm <marc@ihm.name>
To: libffi-discuss@sourceware.org
Subject: New user of libffi
Date: Sun, 02 Jun 2019 06:07:00 -0000 [thread overview]
Message-ID: <1fa2914b-a8f5-969d-832b-4aa34e38e686@ihm.name> (raw)
Hi,
just wanted to tell, that yabasic (www.yabasic.de) now is a grateful
user of libffi too ...
I was really amazed on how easy it is to use libffi (linux and windows)
and the absence of mysterious segfaults :-)
Thanx everybody for this amazaning software !
best regards,
Marc Ihm
reply other threads:[~2019-06-02 6:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1fa2914b-a8f5-969d-832b-4aa34e38e686@ihm.name \
--to=marc@ihm.name \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).