From: David Kastrup <dak@gnu.org>
To: guile-user@gnu.org
Subject: Re: Guile foreign object interface
Date: Tue, 07 Mar 2017 23:31:29 +0100 [thread overview]
Message-ID: <87r32867ni.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 877f40svma.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> skribis:
>
>> I am not so sure about about this one. I think it's not accurate to
>> characterize beginning to replace a 25-year-old C API (SMOBs) as
>> "churn".
>
> I think the point is that there’s lots of code out there that rely on
> SMOBs and we shouldn’t break it overnight, precisely because that API
> is this old.
>
> Of course, I agree that pushing users towards an improved API is the
> right thing long term, no argument here.
Shrug. LilyPond has all of its SMOB usage condensed into few C++
classes, so it is comparatively easy to migrate to a different API as
long as it offers comparable functionality.
Which it doesn't (namely the ability of marking objects reached through
STL-managed data structures). So it's pretty pointless to "push users
towards an improved API" and hardly "the right thing".
--
David Kastrup
next prev parent reply other threads:[~2017-03-07 22:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1644439317.409814.1488469678720.ref@mail.yahoo.com>
2017-03-02 15:47 ` Guile foreign object interface Mike Gran
2017-03-06 20:26 ` Andy Wingo
2017-03-06 20:26 ` Andy Wingo
2017-03-07 13:44 ` Ludovic Courtès
2017-03-07 14:21 ` Andy Wingo
2017-03-07 20:02 ` Ludovic Courtès
2017-03-07 22:31 ` David Kastrup [this message]
2017-03-08 20:59 ` Ludovic Courtès
2017-03-08 23:00 ` David Kastrup
2017-03-09 5:49 ` Thien-Thi Nguyen
2017-03-09 21:59 ` David Kastrup
2017-03-09 12:09 ` Ludovic Courtès
2017-03-09 15:47 ` Eli Zaretskii
2017-03-09 17:26 ` Ludovic Courtès
2017-03-09 18:31 ` Eli Zaretskii
2017-03-09 19:56 ` Andy Wingo
2017-03-10 7:38 ` Eli Zaretskii
2017-03-10 8:06 ` Andy Wingo
2017-03-10 8:47 ` David Kastrup
2017-03-10 10:15 ` Arne Babenhauserheide
2017-03-10 10:55 ` David Kastrup
2017-03-11 16:31 ` Arne Babenhauserheide
2017-03-11 17:26 ` David Kastrup
2017-03-11 20:32 ` Arne Babenhauserheide
2017-03-09 22:38 ` David Kastrup
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=87r32867ni.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=guile-user@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).