From: Eli Zaretskii <eliz@gnu.org>
To: ahmed.taahir@gmail.com
Cc: guile-devel@gnu.org
Subject: Re: Exception-safety for C++ code integrated with Guile.
Date: Tue, 24 Feb 2015 21:36:52 +0200 [thread overview]
Message-ID: <838ufn6qzv.fsf@gnu.org> (raw)
In-Reply-To: <4194214.B3z6dDOsXA@basis>
> From: Taahir Ahmed <ahmed.taahir@gmail.com>
> Cc: guile-devel@gnu.org
> Date: Tue, 24 Feb 2015 13:21:48 -0600
>
> From looking at the libunwind source, the only os-dependent code is a single
> function for looking through an elf image.
So it's only good for platforms that use ELF? If so, none of Windows
GNU-based environments will do, they all use PE-COFF.
> What are the platforms that Guile supports? (I can't find a comprehensive list
> anywhere).
That's a good question, I hope that people here will know the answer
(I don't, sorry).
next prev parent reply other threads:[~2015-02-24 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 21:59 Exception-safety for C++ code integrated with Guile Taahir Ahmed
2015-02-24 18:52 ` Eli Zaretskii
2015-02-24 19:21 ` Taahir Ahmed
2015-02-24 19:36 ` Eli Zaretskii [this message]
2015-02-24 19:59 ` Taahir Ahmed
2015-03-10 21:15 ` Andy Wingo
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=838ufn6qzv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=ahmed.taahir@gmail.com \
--cc=guile-devel@gnu.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).