From: Kevin Ryde <user42@zip.com.au>
Subject: Re: deprecated features
Date: Tue, 23 Jan 2007 12:03:33 +1100 [thread overview]
Message-ID: <877ivev9ju.fsf@zip.com.au> (raw)
In-Reply-To: <45B55C06.2000603@xs4all.nl> (Han-Wen Nienhuys's message of "Tue, 23 Jan 2007 01:51:18 +0100")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
> If not now, is there any sort of timescale for when this is scheduled?
Hopefully never for many bits. I think several things have been
tagged unnecessarily.
If something is not very nice, then by all means shunt it off to a
corner of the manual and advertise the good way. But taking stuff out
is bad.
> I think it is reasonable to let deprecated interfaces live for one stable
> release,
You yourself have complained about things changed and removed, no?
SCM_STRING_CHARS perhaps ... :-)
One stable is much too short. Surely it's not reasonable to expect
everyone to review all their programs on every stable release.
> to allow people to update broken programs, and remove them after
> that.
My point is that many bits in question aren't and weren't broken. Not
too nice, sure, but not utterly hopeless.
_______________________________________________
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 1:03 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 [this message]
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
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=877ivev9ju.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).