From: Dirk Herrmann <dirk@dirk-herrmanns-seiten.de>
Subject: Backward compatibility
Date: Sat, 06 Sep 2003 11:33:59 +0200 [thread overview]
Message-ID: <3F59AA07.5010300@dirk-herrmanns-seiten.de> (raw)
Hello together,
I would like to remove the SCM_IM_ definitions from the public
interface. Also, the definition of ilocs should not be public. These
definitions should only be used as an internal interface, for example
between memoization and execution. To make this possible and to clean up
certain issues, I have some ideas about changing the type codes of
immediates.
This, however, would influence the backwards compatibility. Later code
would remain source code compatible, but not binary compatible. That is,
the code would need to be recompiled.
I realize that you, Marius, have put a lot of effort to make guile
backwards compatible. Do you intend to make it binary backwards
compatible, or is it sufficient for you if Guile was sourcecode
backwards compatible?
Best regards
Dirk
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-09-06 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 9:33 Dirk Herrmann [this message]
2003-09-07 1:27 ` Backward compatibility Rob Browning
2003-09-07 22:41 ` 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=3F59AA07.5010300@dirk-herrmanns-seiten.de \
--to=dirk@dirk-herrmanns-seiten.de \
/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).