From: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: Re-addition of deprecated stuff to 1.7.
Date: 26 Apr 2003 09:31:23 +0100 [thread overview]
Message-ID: <m3d6j9d5ic.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <ljptoeknrl.fsf@burns.dt.e-technik.uni-dortmund.de>
>>>>> "Marius" == Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
Marius> Hi, I have started to re-add most of the things that were
Marius> deprecated in 1.6 and removed in 1.7. I hope everyone
Marius> agrees that this is OK.
Yes, but can it be done in a way that the back compatible bits are
kept separate from the core? A while ago you mentioned something like
_GNU_SOURCE, which seems exactly right to me.
For example, an application would just say
#define _GUILE_SOURCE 1.6
#include <libguile.h>
And a 1.7.x/1.8.x libguile.h would have something at the end like
#if _GUILE_SOURCE = 1.6
#include <guile/compat-1.6.h>
#endif
Similarly, any back compatibility object code would ideally be in
libguile-compat-1.6.so; although I'm not sure how to make the linking
in of the extra library as automatic as possible for the application
author.
Marius> The idea is that we should backwards compatability for a
Marius> longer time when it is easy enough to do. I am adding the
Marius> things in as clean a way as possible, so that they do not
Marius> get in the way of the mainline code.
It's possible that I may have described what you are already doing,
then :-)
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-04-26 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 18:04 Re-addition of deprecated stuff to 1.7 Marius Vollmer
2003-04-26 8:31 ` Neil Jerram [this message]
2003-05-17 17:22 ` Marius Vollmer
2003-05-17 17:47 ` Rob Browning
2003-05-17 17:57 ` Marius Vollmer
2003-05-17 18:12 ` Bruce Korb
2003-06-01 18:27 ` Marius Vollmer
2003-06-01 19:56 ` Bruce Korb
2003-06-09 19:46 ` Marius Vollmer
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=m3d6j9d5ic.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@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).