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
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
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
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
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,
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
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
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
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
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
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
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
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.
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.
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
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
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
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
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
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
20 matches
Mail list logo
