From: David Kastrup <dak@gnu.org>
To: 18495@debbugs.gnu.org
Subject: bug#18495: Alternatives!?!
Date: Thu, 18 Sep 2014 10:50:21 +0200 [thread overview]
Message-ID: <87lhphs46q.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <1411025555-32284-1-git-send-email-dak@gnu.org>
Well, since the obvious fallback of using SCM_SMOB_OBJECT_1_LOC is
barred since _all_ of SCM_SMOB_OBJECT_LOC, SCM_SMOB_OBJECT_0_LOC,
SCM_SMOB_OBJECT_1_LOC, SCM_SMOB_OBJECT_2_LOC, SCM_SMOB_OBJECT_3_LOC are
broken, will there be something like an official guarantee that using
the undocumented SCM_SMOB_OBJECT_N_LOC will be supported for several
years? Or is one supposed to use the undocumented SCM_CELL_OBJECT_LOC
instead?
I don't see any _documented_ accessor to SMOB cell locations that would
not be broken in the current source.
This is sort of important.
--
David Kastrup
next prev parent reply other threads:[~2014-09-18 8:50 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 ` David Kastrup [this message]
2014-09-20 12:42 ` bug#18495: Alternatives!?! Mark H Weaver
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=87lhphs46q.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=18495@debbugs.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).