[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18495: Alternatives!?!
|
From: |
Mark H Weaver |
|
Subject: |
bug#18495: Alternatives!?! |
|
Date: |
Sat, 20 Sep 2014 08:42:49 -0400 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
David Kastrup <address@hidden> 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
- bug#18495: [PATCH] Fix SCM_SMOB_OBJECT_LOC, David Kastrup, 2014/09/18
- bug#18495: Alternatives?, David Kastrup, 2014/09/18
- bug#18495: Alternatives!?!, David Kastrup, 2014/09/18
- bug#18495: Alternatives!?!,
Mark H Weaver <=
- bug#18495: [PATCH] Fix SCM_SMOB_OBJECT{_,_0_,_1_,_2_,_3_}LOC, David Kastrup, 2014/09/18