From: Andy Wingo <wingo@pobox.com>
To: Johan Hidding <johannes.hidding@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: sample guile-2.0 extension in manual
Date: Mon, 09 Jan 2012 16:19:20 +0100 [thread overview]
Message-ID: <8762gkaop3.fsf@pobox.com> (raw)
In-Reply-To: <CAEz5FLaMyaKr0zH7y+0f54teOG2NzFu3RytpTB0biwz81bgFvg@mail.gmail.com> (Johan Hidding's message of "Fri, 5 Aug 2011 17:16:39 +0200")
Hi Johan,
On Fri 05 Aug 2011 17:16, Johan Hidding <johannes.hidding@gmail.com> writes:
> Hi, In manual chapter 5.3.1 there is a small example program. Using
> GCC 4.6, this only compiles with -fpermissive, unless an explicit
> reinterpret_cast<scm_t_subr> (which is an alias for (void *)) is
> used. Should this be considered a (minor) bug in the manual?
I don't think so -- the code is correct C. AFAIK You will only get
errors there if you are compiling with g++, not gcc.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2012-01-09 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 15:16 sample guile-2.0 extension in manual Johan Hidding
2012-01-09 15:19 ` Andy Wingo [this message]
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=8762gkaop3.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
--cc=johannes.hidding@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).