From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Thomas Morley Newsgroups: gmane.lisp.guile.devel,gmane.lisp.guile.user Subject: Re: GNU Guile 2.1.7 released (beta) Date: Tue, 28 Feb 2017 00:00:40 +0100 Message-ID: References: <87y3x3zt6v.fsf@pobox.com> <87tw7kviu6.fsf@pobox.com> <87k28fmqhu.fsf@web.de> <8760jwvnql.fsf@pobox.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1488236460 2132 195.159.176.226 (27 Feb 2017 23:01:00 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 27 Feb 2017 23:01:00 +0000 (UTC) Cc: Arne Babenhauserheide , guile-user@gnu.org, guile-devel@gnu.org To: Andy Wingo Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Feb 28 00:00:54 2017 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ciUHg-0007wI-Oi for guile-devel@m.gmane.org; Tue, 28 Feb 2017 00:00:48 +0100 Original-Received: from localhost ([::1]:57430 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ciUHl-0000Sp-37 for guile-devel@m.gmane.org; Mon, 27 Feb 2017 18:00:53 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46601) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ciUHd-0000R9-8s for guile-devel@gnu.org; Mon, 27 Feb 2017 18:00:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ciUHc-0003oj-5P for guile-devel@gnu.org; Mon, 27 Feb 2017 18:00:45 -0500 Original-Received: from mail-qk0-x22c.google.com ([2607:f8b0:400d:c09::22c]:32805) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ciUHZ-0003mk-GR; Mon, 27 Feb 2017 18:00:41 -0500 Original-Received: by mail-qk0-x22c.google.com with SMTP id n127so122285884qkf.0; Mon, 27 Feb 2017 15:00:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=X5WbeXy0PpznXGCA3J+K52L4RaHquKKHQto7OvayEC4=; b=XRxHOL9k8Cms/eSNeL3Nws/NXTsuSpZuBrSyMP9/3chxyBuUUNJsT946jNAOEGCPy4 O7qo5unVMweyn5Kyaw0Uc+tCRaII+BbSTTHKsGwwEPAkno+xCp4ktxpcIZJzEmR0+2L1 VTixLaAbig6kH+mtg5S7s/LV5FqqBZkYNSiidIFDH7QeY7FKghwXXu+smagKLQTGZGzK G35DO3s1rpp/6Zl9nZuwYrUTAhBEbcni9Fz4suvTL1mKCses9entlfDjEi+OymX5GaXI UsZL542f/0tLXcx9ApCVRid2tYrd7mHfJRxV+5cSnwlgHmLgs5FJevIi11cGukObnpVc ShMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=X5WbeXy0PpznXGCA3J+K52L4RaHquKKHQto7OvayEC4=; b=McaoyXrniwaGorv37eIZMkIeo3/Q2IQoceo2RKl4IabGANfy8Iv/MMQhx4bZMTZL3W PA1QB9gPS3bb10fT3vUQr/WlynlWOnjs8nkF3SIxMnLKAcRg+/74qzvZjD31RV9/5xgj ua9MqpoZWvssJyxajhhrFArYn8pAgVXqsJ7acyxDlai3H5imtEtCzO0QMHojq+LFYULr lljinuX111dOhSLZfd/OMqVbt26nU9F9FSktaPGkVcGSC/as3B2iI+098CtsMqDviQPB FgQNtLOxzwOXxT/BuyBzDB8pWl2DPLrP8gF6jxVIOOkqyndVpHcA7ta4/inQvrP2it3e bQhQ== X-Gm-Message-State: AMke39n/O9VxHYtw0B35gIeC5LzY+IvPHOSyDJKLrZJF1/dk4yYB0wHbz0WixnJ82fybpJ8rFae/XdlDSAF2Lg== X-Received: by 10.233.237.2 with SMTP id c2mr20031572qkg.227.1488236440771; Mon, 27 Feb 2017 15:00:40 -0800 (PST) Original-Received: by 10.140.89.136 with HTTP; Mon, 27 Feb 2017 15:00:40 -0800 (PST) In-Reply-To: <8760jwvnql.fsf@pobox.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400d:c09::22c X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: "guile-devel" Xref: news.gmane.org gmane.lisp.guile.devel:18959 gmane.lisp.guile.user:13348 Archived-At: 2017-02-26 18:57 GMT+01:00 Andy Wingo : > On Fri 24 Feb 2017 18:46, Arne Babenhauserheide 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 > Hi, I'm more a musician and LilyPond power-user. As a developer I'm focused on creating new, directly usable functionality. So I feel pretty much out of my league here... Though, I hope a view from a LilyPond user may find some interest. Due to bug-fixes guile-2.0.12 was the first version which could be used to build LilyPond, afaik. We have now LilyDev-5.1 for use in a VB (with guile-2.10.13), for everyone who wants to work on guilev2 migration. Meanwhile I have a LilyPond-build with guile-2.1.7 on my machine. (With a brute-force fix, simply deleting all functionality related to scm_protects. Replacing it with scm_gc_protect_object as the IRC-log https://gnunet.org/bot/log/guile/2017-01-05 seems to suggest didn't work) The main problems/TODOs are listed here (same for guile-2.0.13 and 2.1.7): https://ao2.it/tmp/lilypond-guile2/TODO With no warranty for completeness. Let me pick some of them: (1) lilypond filename_=E5=90=8D=E5=AD=97.ly returns fatal error: failed files: "filename_??????.ly" (2) Floating point numbers are different in some decimal digits. Possible impact on spacing in a regression-test for utf-8. (3) Most imortant for users: LilyPond slowed down dramatically. Today I tested a huge file: lilypond 2.19.52 with guile-1.8 real 9m8.229s user 6m41.156s sys 0m11.940s lilypond 2.19.56 with guile-2.1.7 real 48m45.225s user 65m43.252s sys 0m6.320s Investigating and fixing those is beyond my current knowledge. Though, that's the current state, afaik. Best, Harm