From: Han-Wen Nienhuys <hanwenn@gmail.com>
To: Ian Hulin <ian@hulin.org.uk>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
guile-devel@gnu.org,
"lilypond-devel@gnu.org" <lilypond-devel@gnu.org>
Subject: Re: %module-public-interface
Date: Tue, 6 Apr 2010 11:00:49 -0300 [thread overview]
Message-ID: <u2yf329bf541004060700g39264096z156f4f658f9b4313@mail.gmail.com> (raw)
In-Reply-To: <4BB5DBF7.6050700@hulin.org.uk>
On Fri, Apr 2, 2010 at 8:58 AM, Ian Hulin <ian@hulin.org.uk> wrote:
>>>>>> How do they use it?
>>>>>>
>>>>>
>>>>> Linking to the evil empire:
>>>>> http://www.google.com/codesearch?hl=en&lr=&q=%25module-public-interface&sbtn=Search
(ehh?)
>> When is the new Lilypond release due?
>>
>>
>
> I'm not the ReleaseMeister for Lilypond; you'll get a better picture by
> talking to Graham Percival (graham@percival-music.ca).
>
> But FWIW it looks like we're on our few last development releases before the
> stable V2.14 comes out. It's near enough for a spoof release announcement
> to have gone out on the mailing list on April 1st which suckered me!
>
> I reckon plans are for Lilypond to stick with Guile V1.8.7 at least until
> the next Lilypond stable version after V2.14, but again, mileage may vary if
> you talk to more experienced Lilypond people.
Is Guile 2.0 already released?
I think it makes sense to forget about guile 2.0 for the 2.14 release,
and require 2.0 for the 2.16 release. We could scrap lots of hairy GC
code if we could move to 2.0 (2.0 supports boehm GC, right?)
> 4. We've already seen the %module-public-interface thing in the Lily C++.
> There's probably more smelly stuff lurking in the C++ interface, which
> won't surface until we start trying to use Guile 2.0 more.
There may be lots of hairiness in the module interface; I sort of made
up functions as I went along, since it was largely undocumented.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2010-04-06 14:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 20:45 %module-public-interface Andy Wingo
2010-03-30 20:56 ` %module-public-interface Ludovic Courtès
2010-03-30 21:07 ` %module-public-interface Andy Wingo
2010-03-30 21:52 ` %module-public-interface Ludovic Courtès
2010-03-30 22:20 ` %module-public-interface Andy Wingo
2010-04-02 0:11 ` %module-public-interface Ian Hulin
2010-04-02 9:37 ` %module-public-interface Ludovic Courtès
2010-04-02 11:58 ` %module-public-interface Ian Hulin
2010-04-02 18:50 ` %module-public-interface Patrick McCarty
2010-04-03 0:52 ` %module-public-interface Graham Percival
2010-04-06 14:00 ` Han-Wen Nienhuys [this message]
2010-04-06 14:32 ` %module-public-interface Ludovic Courtès
2010-04-27 20:34 ` %module-public-interface Andy Wingo
2010-05-15 20:32 ` %module-public-interface Ian Hulin
2010-05-21 9:48 ` %module-public-interface Andy Wingo
2010-03-31 20:42 ` Hierarchical name space Ludovic Courtès
2010-03-31 22:31 ` Andy Wingo
2010-04-07 22:42 ` Julian Graham
2010-04-07 23:01 ` Ludovic Courtès
2010-04-08 7:29 ` Andy Wingo
2010-04-08 8:39 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2020-01-15 6:50 %module-public-interface dsmich
2020-01-15 19:59 ` %module-public-interface Andy Wingo
2007-08-10 13:57 %module-public-interface Andy Wingo
2007-08-10 14:54 ` %module-public-interface Ludovic Courtès
2010-03-30 21:02 ` %module-public-interface Andy Wingo
2010-03-30 21:40 ` %module-public-interface Ludovic Courtès
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=u2yf329bf541004060700g39264096z156f4f658f9b4313@mail.gmail.com \
--to=hanwenn@gmail.com \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
--cc=ian@hulin.org.uk \
--cc=lilypond-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).