Re: Use of null (begin) blocks is deprecated in Guile stable V2.0, use unspecified? and/or *unspecified* instead.

[Ian Hulin]

Hi David,
On 22/11/11 14:02, David Kastrup wrote:
> David Kastrup <address@hidden> writes:
> 
>> Ian Hulin <address@hidden> writes:
>> 
>>> This is forwarded from the Guile bug list.  Bug-squad please
>>> create a LilyPond issue for this - we need to change our code:
>>> 
>>> Files affected appear (according to git grep) to be: 
>>> lily/mensural-ligature.cc lily/system.cc scm/c++.scm 
>>> scm/define-event-classes.scm scm/music-functions.scm
>> 
>> I am responsible for most of those, and will fix them.  No issue 
>> required here.
> 

Thanks one again for the prompt response.

> Pushed to staging.  Sorry for my repeated attempts at sabotaging
> GuileV2 migration.
> 

Don't beat yourself up about stuff like this.

LilyPond started when Guile was a very young project, and there are
quite a few under-the-bonnet work-rounds and kludges in the Lily
interface with Guile which have become cruft as Guile has picked up
changes Lily has needed but the two projects have got out of sync.

Guile V1.8 - V2 is a huge change and we have to do this while keeping
LilyPond (reasonably) backwards-compatible. Meanwhile, you're doing
brain-surgery on the Lily parser which is providing lots of benefits
in terms of simplifying writing Lily code interacting with Scheme.

Sometimes you can get bitten by stuff which has moved on because you
weren't there at the time to ask the right questions.

No-one is blaming you for anything here, you're part of a team of
volunteers working on this on this project, even if sometimes you get
even grumpier than Graham!

Cheers,

Ian