From: Mark H Weaver <mhw@netris.org>
To: David Kastrup <dak@gnu.org>
Cc: 18495-done@debbugs.gnu.org
Subject: bug#18495: Alternatives!?!
Date: Sat, 20 Sep 2014 08:42:49 -0400 [thread overview]
Message-ID: <871tr6mpiu.fsf@yeeloong.lan> (raw)
In-Reply-To: <87lhphs46q.fsf@fencepost.gnu.org> (David Kastrup's message of "Thu, 18 Sep 2014 10:50:21 +0200")
David Kastrup <dak@gnu.org> writes:
> * libguile/smob.h (SCM_SMOB_OBJECT_LOC, SCM_SMOB_OBJECT_0_LOC)
> (SCM_SMOB_OBJECT_1_LOC, SCM_SMOB_OBJECT_2_LOC)
> (SCM_SMOB_OBJECT_3_LOC): These elementary API macros have been broken
> by commit 56164dc47f6616b359f0ad23be208f01a77b55fa in 2009
Ouch. I've pushed this to stable-2.0, commit
8442211ef0029581b35f784489afcf210491fc41. I'm closing this bug.
> will there be something like an official guarantee that using
> the undocumented SCM_SMOB_OBJECT_N_LOC will be supported for several
> years?
I think that's the best option. Just use SCM_SMOB_OBJECT_N_LOC.
Mark
prev parent reply other threads:[~2014-09-20 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 7:32 bug#18495: [PATCH] Fix SCM_SMOB_OBJECT_LOC David Kastrup
2014-09-18 7:39 ` bug#18495: Alternatives? David Kastrup
2014-09-18 8:40 ` bug#18495: [PATCH] Fix SCM_SMOB_OBJECT{_,_0_,_1_,_2_,_3_}LOC David Kastrup
2014-09-18 8:50 ` bug#18495: Alternatives!?! David Kastrup
2014-09-20 12:42 ` Mark H Weaver [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=871tr6mpiu.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=18495-done@debbugs.gnu.org \
--cc=dak@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).