From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Patrick McCarty Newsgroups: gmane.comp.gnu.lilypond.devel,gmane.lisp.guile.devel Subject: Re: %module-public-interface Date: Fri, 2 Apr 2010 11:50:08 -0700 Message-ID: <20100402185008.GA7853@mail.google.com> References: <87zl1pv89p.fsf@gnu.org> <87d3ylv5oe.fsf@gnu.org> <4BB53617.7060700@hulin.org.uk> <87y6h6kxei.fsf@gnu.org> <4BB5DBF7.6050700@hulin.org.uk> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: dough.gmane.org 1270234243 3133 80.91.229.12 (2 Apr 2010 18:50:43 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 2 Apr 2010 18:50:43 +0000 (UTC) Cc: Ludovic =?utf-8?Q?Court=C3=A8s?= , guile-devel@gnu.org, lilypond-devel@gnu.org To: Ian Hulin Original-X-From: lilypond-devel-bounces+gnu-lilypond-devel=m.gmane.org@gnu.org Fri Apr 02 20:50:38 2010 Return-path: Envelope-to: gnu-lilypond-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Nxlwz-0007W6-UH for gnu-lilypond-devel@m.gmane.org; Fri, 02 Apr 2010 20:50:38 +0200 Original-Received: from localhost ([127.0.0.1]:56343 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nxlwz-00061C-C4 for gnu-lilypond-devel@m.gmane.org; Fri, 02 Apr 2010 14:50:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nxlwi-0005zc-M2 for lilypond-devel@gnu.org; Fri, 02 Apr 2010 14:50:20 -0400 Original-Received: from [140.186.70.92] (port=43005 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nxlwh-0005xt-0b for lilypond-devel@gnu.org; Fri, 02 Apr 2010 14:50:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nxlwf-0003nR-Tq for lilypond-devel@gnu.org; Fri, 02 Apr 2010 14:50:18 -0400 Original-Received: from mail-pv0-f169.google.com ([74.125.83.169]:60428) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nxlwd-0003md-Ea; Fri, 02 Apr 2010 14:50:15 -0400 Original-Received: by pvg11 with SMTP id 11so495043pvg.0 for ; Fri, 02 Apr 2010 11:50:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=dVRyTKTBVlPiMxXi+fA6yx0IlH2AcEg1v+dXLYnrC8Y=; b=TotlS3heKAIDCE93rz0oQDYvXy6qeO0rjoeFaJ9kTcnYjgDWeuFvCnre+AvPztq0Oc c413L0sq+0moGu0vjM1FOx9I4NUvCProtXgZJ7QICJoJwRy8Ig5fUqnEsfZgk+Nn4KGl kDXgXnRhgK1RrlpgDDsGUZc4ZRc3RKem+kUv4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=jpwnIDjZppBy7L9L3Etj1TvGyB7WWu3Pag9Bt+8H7UlxXDqL9gpAlPO9k4Egz/VvLQ nu7xz89EgEdZd6otdQhj1sGUCEb/zHFjDln3CdSZR2v3n3ScujMLME8esAfMKWnRXIeQ x1nnaRu1gq1huBIu/RgHnQE4N8PoozeGC+jTU= Original-Received: by 10.115.25.6 with SMTP id c6mr2532359waj.129.1270234214272; Fri, 02 Apr 2010 11:50:14 -0700 (PDT) Original-Received: from mail.google.com (c-71-237-208-179.hsd1.or.comcast.net [71.237.208.179]) by mx.google.com with ESMTPS id 22sm2528450pzk.1.2010.04.02.11.50.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Apr 2010 11:50:13 -0700 (PDT) Content-Disposition: inline In-Reply-To: <4BB5DBF7.6050700@hulin.org.uk> User-Agent: Mutt/1.5.20 (2009-06-14) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: lilypond-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions on LilyPond development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: lilypond-devel-bounces+gnu-lilypond-devel=m.gmane.org@gnu.org Errors-To: lilypond-devel-bounces+gnu-lilypond-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.comp.gnu.lilypond.devel:28277 gmane.lisp.guile.devel:10138 Archived-At: On 2010-04-02, Ian Hulin wrote: > > 3. There's a restriction introduced in Guile V2.0 whereby dynamic > use of define, define-public and variants will cause the guile > compilation to fail with diagnostics. We have these in our basic > Scheme files (lily.scm and lily-library.scm). These compilation > failures currently stop Lilypond building altogether. This is really just a stricter adherence to the Scheme R5RS. (if ...) can only contain *expressions*, IIUC, and (define ...) is a top-level definition, not an expression. But yes, either LilyPond will need to adapt to these stricter guidelines, or Guile will loosen its policy with respect to (if ...) statements. > 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. I think almost everything is fixed on the C++ side now. > Graham, Vincent, is it worth opening a tracker to capture > forward-compatibility issues with Guile? We already have one (sort of): http://code.google.com/p/lilypond/issues/detail?id=963 > Thanks for your feedback so far, Ludo. The other Lily developer who > has done anything with Guile 1.9/V2.0 is Patrick McCarty > (pnorks@gmail.com). That's . I don't want any email reaching the wrong mailbox. :-) -Patrick