[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guile foreign object interface
From: |
Arne Babenhauserheide |
Subject: |
Re: Guile foreign object interface |
Date: |
Sat, 11 Mar 2017 21:32:49 +0100 |
User-agent: |
mu4e 0.9.16; emacs 25.1.1 |
David Kastrup <address@hidden> writes:
>> I did not mean it as option in Lilypond. I meant it as strategic
>> possibility.
>
> As I see it, it's not big enough that strategic guarantees can be given.
> If you need guarantees, you need to invest into the resources needed for
> that.
Using "The official GNU extension language" is typically pretty safe,
since GNU libraries tend to live and stay stable longer than the typical
middle size company.
>> I hope that will change again. I’m sure most people here want Lilypond
>> to be faster with Guile 2.x than with Guile 1.8.
>
> Where is "here"? It would look better, for sure.
Here is the Guile community.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
signature.asc
Description: PGP signature
- Re: Guile foreign object interface, (continued)
- Re: Guile foreign object interface, Ludovic Courtès, 2017/03/09
- Re: Guile foreign object interface, Eli Zaretskii, 2017/03/09
- Re: Guile foreign object interface, Andy Wingo, 2017/03/09
- Re: Guile foreign object interface, Eli Zaretskii, 2017/03/10
- Re: Guile foreign object interface, Andy Wingo, 2017/03/10
- Re: Guile foreign object interface, David Kastrup, 2017/03/10
- Re: Guile foreign object interface, Arne Babenhauserheide, 2017/03/10
- Re: Guile foreign object interface, David Kastrup, 2017/03/10
- Re: Guile foreign object interface, Arne Babenhauserheide, 2017/03/11
- Re: Guile foreign object interface, David Kastrup, 2017/03/11
- Re: Guile foreign object interface,
Arne Babenhauserheide <=
- Re: Guile foreign object interface, David Kastrup, 2017/03/09