From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: RFD: drop the GH interface.
Date: Sun, 14 Sep 2008 18:19:10 +0200 [thread overview]
Message-ID: <49dd78620809140919k341bba56w3c3178ecb4cd6d4e@mail.gmail.com> (raw)
In-Reply-To: <87wshgl5sd.fsf@gnu.org>
2008/9/13 Ludovic Courtès <ludo@gnu.org>:
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
>> The GH interface was marked as deprecated in
>>
>> commit a0143ebc24c24198e0dfce9b80f3648feb706226
>> Author: Neil Jerram <neil@ossau.uklinux.net>
>> Date: Wed Jun 20 22:08:19 2001 +0000
>>
>> * Explain GH deprecation & plan for scm documentation.
>>
>>
>> Let's really drop it now.
>
> Why? It doesn't cost much to keep it, does it?
My view: it doesn't cost much, but it does cost something. For
example, every time one greps the code to find all uses of a libguile
function/variable/macro, the GH code means that there is a bit more to
look at. In general, I think less code is better, so we would need a
good reason for keeping the GH code, and we don't need an especially
compelling reason to throw it away.
Therefore, I vote for dropping it.
Neil
next prev parent reply other threads:[~2008-09-14 16:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-13 3:08 RFD: drop the GH interface Han-Wen Nienhuys
2008-09-13 10:05 ` Ludovic Courtès
2008-09-14 16:19 ` Neil Jerram [this message]
2008-09-14 18:29 ` Han-Wen Nienhuys
2008-09-18 5:37 ` Han-Wen Nienhuys
2008-09-18 8:07 ` Ludovic Courtès
2008-09-18 9:07 ` Neil Jerram
2008-09-18 13:37 ` Ludovic Courtès
2008-09-20 23:11 ` Han-Wen Nienhuys
2008-09-28 20:47 ` Han-Wen Nienhuys
2008-09-28 20:58 ` Ludovic Courtès
2008-09-18 15:04 ` Bruce Korb
2008-09-19 21:57 ` Greg Troxel
2008-09-21 9:40 ` Neil Jerram
2008-09-21 18:02 ` Bruce Korb
2008-09-22 15:16 ` Ludovic Courtès
2008-09-22 20:12 ` Neil Jerram
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=49dd78620809140919k341bba56w3c3178ecb4cd6d4e@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).