Re: [Lilypond-auto] Issue 4474 in lilypond: Move ly-syntax-constructors into separate module

[lilypond]

Updates:
        Status: Fixed
        Labels: -Patch-push Fixed_2_19_23

Comment #7 on issue 4474 by address@hidden: Move ly-syntax-constructors into  
separate module
https://code.google.com/p/lilypond/issues/detail?id=4474

Pushed to staging as
commit 8499cabe34365c7160ff32f777d3db428b8f8200
Author: David Kastrup <address@hidden>
Date:   Sat Jun 27 13:35:20 2015 +0200

    Issue 4474/6: Combine lyric-combine and lyric-combine-music

commit 873f9fd2771a59c1f24d37b389d2e98107fd109d
Author: David Kastrup <address@hidden>
Date:   Sat Jun 27 13:34:36 2015 +0200

    Issue 4474/5: Provide with-location macro

commit f77ac196c7f5fba8a5a0fd23f1b1d9758e7e6024
Author: David Kastrup <address@hidden>
Date:   Thu Jun 25 19:20:15 2015 +0200

    Issue 4474/4: Replace define-loc with more flexible use of here! command

    Since we are now in a separate module, namespace pollution is not an  
issue.

commit 7a758ef70da39d3b1fb137ce8b5333a53546b355
Author: David Kastrup <address@hidden>
Date:   Thu Jun 25 18:08:34 2015 +0200

    Issue 4474/3: Make all of ly-syntax-constructors.scm a separate module

    That allows putting all the constructors into exported symbols while
    keeping local definitions private.  Since we access this module only
    from C++, not even the exported symbols appear in a normal LilyPond
    session.

commit 398c87d330f24a3838553158e388c42e8fe132cb
Author: David Kastrup <address@hidden>
Date:   Thu Jul 2 16:37:13 2015 +0200

    Issue 4474/2: Export get-next-unique-voice-name from lily module

commit d613b697d6eda2f91df86c1c7205b4344adaaea4
Author: David Kastrup <address@hidden>
Date:   Thu Jun 25 17:07:26 2015 +0200

    Issue 4474/1: Move syntax constructors into separate module

commit bc7e3d9a7b1a171e13bbd37b76ed00d9394b4d22
Author: David Kastrup <address@hidden>
Date:   Sat Jun 27 13:45:02 2015 +0200

    Run scripts/auxiliar/fixscm.sh scm/ly-syntax-constructors.scm


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings