From: Bruce Korb <bkorb@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: deprecated features
Date: Tue, 23 Jan 2007 15:35:44 -0800 [thread overview]
Message-ID: <45B69BD0.4020206@gnu.org> (raw)
In-Reply-To: <45B695F3.1090604@xs4all.nl>
Han-Wen Nienhuys wrote:
> Well, as long as we keep 'supporting' the 1.4 interfaces, there is little
> incentive for developers to upgrade to the 1.6 or 1.8 API.
Let me be clear about this: it is (most likely) not the developers.
It is my clients. Some of them upgrade to bleeding edge Guile and
the obsoleted interfaces choke my program. I update the interfaces
and somebody running on a platform still on Guile 1.4 complains that
it chokes and dies on their system. I could, of course, incorporate
the Guile library into my project, but I've determined that that is
way, way, way over the top. If the interfaces are not stable enough
for me to readily be able to support the current active platforms,
then it is changing too quickly. As it is, I have a long collection
of interface macros that wrap around Guile interfaces. Maintaining
that isn't fun. :( [even less fun is the scm_c_eval_string_from_file_line()
thing, the subject of posts in the past...]
WRT the BSD distro: It's been a couple of years since I encountered
the issue. I don't actively track it. A friend at UofU lets me play
on some of his build platforms, so I'll try to remember to check next
time I log in there. I'm certain it is pretty old.
Cheers - Bruce
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-01-23 23:35 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 [this message]
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
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=45B69BD0.4020206@gnu.org \
--to=bkorb@gnu.org \
--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).