From: "Hans Åberg" <haberg-1@telia.com>
To: Arun Isaac <theroarofthedragon@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: C++ Foreign Function Interface
Date: Fri, 11 Mar 2016 23:40:55 +0100 [thread overview]
Message-ID: <42BB375A-66DE-4517-A2C4-4550867C4425@telia.com> (raw)
In-Reply-To: <87vb4s4vma.fsf@gmail.com>
> On 11 Mar 2016, at 21:17, Arun Isaac <theroarofthedragon@gmail.com> wrote:
>
> Hans Åberg <haberg-1@telia.com> writes:
>
>> You will have to write it yourself. It has been discussed before on
>> this list [1].
>
> In one of the messages in the earlier thread, I found a link to
> https://isocpp.org/wiki/faq/mixing-c-and-cpp
>
> That page gives me some idea of how I can write C wrappers for my C++
> library.
When calling C++ from C, you can’t pass a C++ exception through the C code. So in my example code, there are conversions between C++ and Guile exceptions.
next prev parent reply other threads:[~2016-03-11 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 18:18 C++ Foreign Function Interface Arun Isaac
2016-03-10 21:17 ` Chris Vine
2016-03-11 17:09 ` Hans Åberg
2016-03-11 20:17 ` Arun Isaac
2016-03-11 22:40 ` Hans Åberg [this message]
2016-03-14 16:04 ` Arun Isaac
2016-03-14 19:22 ` Chris Vine
2016-03-14 21:12 ` Jan Wedekind
2016-03-11 23:36 ` David Pirotte
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42BB375A-66DE-4517-A2C4-4550867C4425@telia.com \
--to=haberg-1@telia.com \
--cc=guile-user@gnu.org \
--cc=theroarofthedragon@gmail.com \
/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).