Re: Problem with guile-2.9.1-prerelease

2018-10-14 Thread Thomas Morley
Am So., 14. Okt. 2018 um 11:22 Uhr schrieb Thomas Morley : > > Am Fr., 12. Okt. 2018 um 01:45 Uhr schrieb Thomas Morley > : > > > Tomorrow I'll redo a full 'make doc'. David, I forgot to mention: A new run of a full 'make doc' with your patch "Use different `values' implementation of Guilev2" and

Re: Problem with guile-2.9.1-prerelease

2018-10-14 Thread Thomas Morley
Am Fr., 12. Okt. 2018 um 01:45 Uhr schrieb Thomas Morley : > Tomorrow I'll redo a full 'make doc'. > Testing your changes with guile-2.2.4 and guile-1.8 is postponed for > tomorrow as well. To facilitate testing I had to change my local setup to compare multiple combinations of guile-versions wit

Re: Problem with guile-2.9.1-prerelease

2018-10-12 Thread David Kastrup
Thomas Morley writes: > Am Do., 11. Okt. 2018 um 21:25 Uhr schrieb Thomas Morley > : > > 'make doc' (without rest-positioning.ly) now ended successfully (with > guile-2.9.1) > > I then tried to apply your patch to my lilypond-git-guile-3.0 but I've got: > $ git apply 0001-Use-different-values-imp

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Thomas Morley
Am Do., 11. Okt. 2018 um 21:25 Uhr schrieb Thomas Morley : > > Am Do., 11. Okt. 2018 um 20:57 Uhr schrieb David Kastrup : > > > > Thomas Morley writes: > > > > > Am Do., 11. Okt. 2018 um 20:17 Uhr schrieb Karlin High > > > : > > >> > > >> On 10/11/2018 12:59 PM, David Kastrup wrote: > > >> > we s

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread David Kastrup
Thomas Morley writes: > Am Do., 11. Okt. 2018 um 21:54 Uhr schrieb David Kastrup : >> >> Thomas Morley writes: >> >> > Am Do., 11. Okt. 2018 um 20:57 Uhr schrieb David Kastrup : >> >> >> >> Could you reinstate the regtest and try this untested patch? Not >> >> necessarily in that order since, w

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Thomas Morley
Am Do., 11. Okt. 2018 um 21:54 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Do., 11. Okt. 2018 um 20:57 Uhr schrieb David Kastrup : > >> > >> Could you reinstate the regtest and try this untested patch? Not > >> necessarily in that order since, well, the patch might well not eve

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread David Kastrup
Thomas Morley writes: > Am Do., 11. Okt. 2018 um 20:57 Uhr schrieb David Kastrup : >> >> Could you reinstate the regtest and try this untested patch? Not >> necessarily in that order since, well, the patch might well not even >> compile. Or work correctly. > > Will do, though I'll first wait fo

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Thomas Morley
Am Do., 11. Okt. 2018 um 20:57 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Do., 11. Okt. 2018 um 20:17 Uhr schrieb Karlin High > > : > >> > >> On 10/11/2018 12:59 PM, David Kastrup wrote: > >> > we should be able to add code that will run under all versions. > >> > >> The guile

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread David Kastrup
Carl Sorensen writes: > On 10/11/18, 12:35 PM, "lilypond-devel on behalf of Urs Liska" > li...@openlilylib.org> wrote: > > > > Am 11. Oktober 2018 20:17:45 MESZ schrieb Karlin High > : > >On 10/11/2018 12:59 PM, David Kastrup wrote: > >What level of optimism is appropriat

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread David Kastrup
Thomas Morley writes: > Am Do., 11. Okt. 2018 um 20:17 Uhr schrieb Karlin High : >> >> On 10/11/2018 12:59 PM, David Kastrup wrote: >> > we should be able to add code that will run under all versions. >> >> The guile-devel post linked in the OP indicates that Guile 3 should have >> greatly improv

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread David Kastrup
Karlin High writes: > On 10/11/2018 12:59 PM, David Kastrup wrote: >> we should be able to add code that will run under all versions. > > The guile-devel post linked in the OP indicates that Guile 3 should > have greatly improved performance over Guile 2. Maybe even better than > LilyPond's curre

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Carl Sorensen
On 10/11/18, 12:35 PM, "lilypond-devel on behalf of Urs Liska" wrote: Am 11. Oktober 2018 20:17:45 MESZ schrieb Karlin High : >On 10/11/2018 12:59 PM, David Kastrup wrote: >What level of optimism is appropriate for that claim? I don't think that tells us very m

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Urs Liska
Am 11. Oktober 2018 20:17:45 MESZ schrieb Karlin High : >On 10/11/2018 12:59 PM, David Kastrup wrote: >> we should be able to add code that will run under all versions. > >The guile-devel post linked in the OP indicates that Guile 3 should >have >greatly improved performance over Guile 2. Maybe

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Thomas Morley
Am Do., 11. Okt. 2018 um 20:17 Uhr schrieb Karlin High : > > On 10/11/2018 12:59 PM, David Kastrup wrote: > > we should be able to add code that will run under all versions. > > The guile-devel post linked in the OP indicates that Guile 3 should have > greatly improved performance over Guile 2. May

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Karlin High
On 10/11/2018 12:59 PM, David Kastrup wrote: we should be able to add code that will run under all versions. The guile-devel post linked in the OP indicates that Guile 3 should have greatly improved performance over Guile 2. Maybe even better than LilyPond's current Guile 1.8. What level of

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Thomas Morley
Am Do., 11. Okt. 2018 um 20:00 Uhr schrieb David Kastrup : > Sorry, I overlooked that you already boiled this down to a minimal > example using $@. I am sort-of sure that this will be due to the > internals of (values ...) having changed in some manner. The "wrong > type argument" will be for tr

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread David Kastrup
David Kastrup writes: > I think Guile-2.0 introduced some mechanism for doing so but retained > compatibility, and this compatibility has now gone out of the window. > So with some luck and some #ifdef GUILEV2 guard, we should be able to > add code that will run under all versions. I'll take a l

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread David Kastrup
Thomas Morley writes: > Am Do., 11. Okt. 2018 um 19:34 Uhr schrieb David Kastrup : >> >> Thomas Morley writes: >> >> > Hi, >> > >> > according to this post: >> > https://lists.gnu.org/archive/html/guile-devel/2018-10/msg0.html >> > guile prepares to release 3.0 soon. >> > >> > I tried to tes

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread Thomas Morley
Am Do., 11. Okt. 2018 um 19:34 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Hi, > > > > according to this post: > > https://lists.gnu.org/archive/html/guile-devel/2018-10/msg0.html > > guile prepares to release 3.0 soon. > > > > I tried to test LilyPond with the guile-2.9.1-prel

Re: Problem with guile-2.9.1-prerelease

2018-10-11 Thread David Kastrup
Thomas Morley writes: > Hi, > > according to this post: > https://lists.gnu.org/archive/html/guile-devel/2018-10/msg0.html > guile prepares to release 3.0 soon. > > I tried to test LilyPond with the guile-2.9.1-prelease. > Checking out our dev/guile-v2-work-branch, rebasing, applying several

Problem with guile-2.9.1-prerelease

2018-10-11 Thread Thomas Morley
Hi, according to this post: https://lists.gnu.org/archive/html/guile-devel/2018-10/msg0.html guile prepares to release 3.0 soon. I tried to test LilyPond with the guile-2.9.1-prelease. Checking out our dev/guile-v2-work-branch, rebasing, applying several patches (working with guile-2.2.4) as