Re: Backward compatibility status

[Ludovic Courtès]

Hi Patrick,

Patrick McCarty <address@hidden> writes:

> 2010/3/6 Ludovic Courtès <address@hidden>:

[...]

>> | Name                                  | Cause                              
>>              |
>> |---------------------------------------+-------------------------------------------------|
>> | lilypond-2.13.9                       | `scm_internal_hash_fold' & 
>> `scm_t_hash_fold_fn' |
>
> Is this something that should be fixed in LilyPond?

I think so, yes (especially since ‘scm_internal_hash_fold’ was intended
to be sort-of internal.)

> For reference, I'm fairly certain this build failure was introduced
> with Guile commit a07010bf1828704edd9a40cadb0eaf820b8f3638.

Yes, that’s the one.

> If I add the typedefs to the appropriate LilyPond header file and use
> them, the problem goes away, but I don't know if there are unexpected
> side effects of this.

I think you want a fix that retains compatibility with 1.8.  How about
having a ‘configure’ test checking for this typedef?

> I am unable to test any further, because there are more build failures
> down the pipeline.  :-)

Heh.  Let us know what other Guile-related failures you stumble upon!

Thanks,
Ludo’.