From: Kevin Ryde <user42@zip.com.au>
To: hanwen@xs4all.nl
Cc: guile-devel@gnu.org
Subject: Re: Eval options macro: backward compatibility?
Date: Thu, 25 Jan 2007 08:05:33 +1100 [thread overview]
Message-ID: <87ps94t9sy.fsf@zip.com.au> (raw)
In-Reply-To: <eoqnqp$ki1$1@sea.gmane.org> (Han-Wen Nienhuys's message of "Fri, 19 Jan 2007 16:24:15 +0100")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
> what is the status of the eval options structure wrt binary compatibility?
I remeber now: changing the size of a data object in a shared library
breaks mainlines using it, or even just taking its address. And both
mainline and the library are broken, since the object is truncated to
the smaller size for both. This is a bit subtle, but it bit for
instance in some of the old Xaw replacement libraries in the past.
If you think noone is using it then rename to scm_i_. Or if you think
it's used then growing breaks it so take the opportunity to change to
a pointer at the same time.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2007-01-24 21:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 15:24 Eval options macro: backward compatibility? Han-Wen Nienhuys
2007-01-20 14:35 ` Ludovic Courtès
2007-01-22 14:18 ` Han-Wen Nienhuys
2007-01-22 20:48 ` Kevin Ryde
2007-01-23 0:51 ` deprecated features Han-Wen Nienhuys
2007-01-23 1:03 ` Kevin Ryde
2007-01-23 1:20 ` Han-Wen Nienhuys
2007-01-23 14:50 ` Bruce Korb
2007-01-23 22:45 ` Han-Wen Nienhuys
2007-01-23 23:20 ` Bruce Korb
2007-01-24 0:44 ` Han-Wen Nienhuys
2007-01-24 0:10 ` Bruce Korb
2007-01-23 23:10 ` Han-Wen Nienhuys
2007-01-23 23:35 ` Bruce Korb
2007-01-24 0:38 ` Han-Wen Nienhuys
2007-01-24 22:44 ` Kevin Ryde
2007-01-22 15:28 ` Eval options macro: backward compatibility? Han-Wen Nienhuys
2007-01-22 20:50 ` Kevin Ryde
2007-01-24 21:05 ` Kevin Ryde [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=87ps94t9sy.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).