From: Andy Wingo <wingo@pobox.com>
To: Arne Babenhauserheide <arne_bab@web.de>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: GNU Guile 2.1.7 released (beta)
Date: Sun, 26 Feb 2017 18:57:38 +0100 [thread overview]
Message-ID: <8760jwvnql.fsf@pobox.com> (raw)
In-Reply-To: <87k28fmqhu.fsf@web.de> (Arne Babenhauserheide's message of "Fri, 24 Feb 2017 18:46:05 +0100")
On Fri 24 Feb 2017 18:46, Arne Babenhauserheide <arne_bab@web.de> writes:
> The main strategical question I see for that is: Does anything make it
> harder to complete or improve the lilypond transition to Guile 2?
>
> Is there something which would need to be done before 2.2 which could
> make it easier for lilypond developers?
I don't know of any concrete points here. 2.2 is not dissimilar to 2.0.
If you someone like to try to determine exactly what specific bits of
Guile 2.2 impact Lilypond (and indeed any big application using the C
interface), that would be welcome :) I guess I'd start with NEWS to see
what's up.
Andy
next prev parent reply other threads:[~2017-02-26 17:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 10:31 GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-18 14:34 ` GNU Guile 2.1.7 released (beta), SOCK_NONBLOCK Matt Wette
2017-02-21 20:58 ` Andy Wingo
2017-02-18 17:40 ` GNU Guile 2.1.7 released (beta) Matt Wette
2017-02-18 17:48 ` Matt Wette
2017-02-23 18:54 ` Andy Wingo
2017-02-23 20:04 ` Mike Gran
2017-02-23 21:06 ` Andy Wingo
2017-02-24 0:52 ` Break-when [was GNU Guile 2.1.7 released (beta)] Matt Wette
2017-02-24 14:02 ` GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-24 17:46 ` Arne Babenhauserheide
2017-02-26 17:57 ` Andy Wingo [this message]
2017-02-27 19:32 ` Mike Gran
2017-02-27 20:30 ` Andy Wingo
2017-02-27 23:00 ` Thomas Morley
2017-02-28 8:31 ` Andy Wingo
2017-03-05 16:54 ` Thomas Morley
2017-03-01 18:04 ` Arne Babenhauserheide
2017-02-28 0:04 ` David Pirotte
2017-02-28 1:49 ` Daniel Llorens
2017-03-02 20:54 ` David Pirotte
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=8760jwvnql.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=arne_bab@web.de \
--cc=guile-devel@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).