David Kastrup writes:
[...]
I apologize for sending this and the previous mail to the Guile-devel
list in violation of my ban here. I had been of the impression that
this was copied to the LilyPond developer list rather than the Guile
developer list.
Feel free to delete it.
--
Jan Nieuwenhuizen writes:
> David Kastrup writes:
>
> Hi David,
>
>> Shouldn't we worry about switching _to_ guile-2.0 first?
>
> Are you asking for help on this?
Is there any to be had? I got a whole lot of promises from Guile
developers over the years. Basically, whenever
Jan Nieuwenhuizen writes:
That was a copy of the old one again, here is the updated v3.
Jan
Only after rebuilding world, I found this morning that the previous
patch did not exactly work as intended. Find version 3 of this patch
attached.
Instead of having scm_call_0 possibly throw and
David Kastrup writes:
Hi David,
> Shouldn't we worry about switching _to_ guile-2.0 first?
Are you asking for help on this?
In any case, I am sure that running guix with nicely coexisting
guile-2.0, guile-2.0++ and guile-next versions can be of great help
here.
Greetings,
Jan
--
Jan
Hi,
Only after rebuilding world, I found this morning that the previous
patch did not exactly work as intended. Find version 3 of this patch
attached.
Instead of having scm_call_0 possibly throw and catching that in
vm.c:(scm_load_compiled_with_vm), now the FALSE_ON_ERROR flag is
propagated