unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Subject: Re: deprecated features
Date: Tue, 23 Jan 2007 02:20:36 +0100	[thread overview]
Message-ID: <45B562E4.4000105@xs4all.nl> (raw)
In-Reply-To: <877ivev9ju.fsf@zip.com.au>

Kevin Ryde escreveu:
>> 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 ... :-)

Perhaps, but I'm for cleaner code. Having to keep deprecated stuff
around (and worse: having to write various deprecation wrappers for
them) is detrimental to code quality.

If the consensus is that removing deprecated features will not ever be
done, then there is little point in marking routines as such, and
writing wrappers to signal their use. We could clean up GUILE by
throwing away all the bookkeeping.

> One stable is much too short.  Surely it's not reasonable to expect
> everyone to review all their programs on every stable release.

I tend to disagree.

At the current release rate of GUILE, I'd expect anyone using GUILE
seriously to run the CVS version.  I do, at least. 

-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2007-01-23  1:20 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 [this message]
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=45B562E4.4000105@xs4all.nl \
    --to=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).