lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 4121 in lilypond: Patch: Store music list and


From: lilypond
Subject: Re: [Lilypond-auto] Issue 4121 in lilypond: Patch: Store music list and markup command argument list names in docstring
Date: Wed, 24 Sep 2014 14:01:32 +0000

Updates:
        Status: Fixed
Labels: -Type-Enhancement -Patch-countdown Type-Maintainability Fixed_2_19_15

Comment #4 on issue 4121 by address@hidden: Patch: Store music list and markup command argument list names in docstring
https://code.google.com/p/lilypond/issues/detail?id=4121

Bypassing countdown in order to get GUILEv2 into shape sooner, pushed to staging as
commit 0fe36c1225b6060ef0431089d41fde5cc6bab3ce
Author: David Kastrup <address@hidden>
Date:   Sat Sep 20 19:57:38 2014 +0200

    Issue 4121/2: Store markup command argument list names in docstring

    For one thing, the doc string does not make a lot of sense without the
    argument list and it cannot reliably be deduced from the doc string
    itself.

    For another, GUILEv2 does not do us the favor of storing the original
    argument list anywhere where it could be retrieved with a useful amount
    of labor.

    While it would be nice to put the types of the arguments into the doc
    string as well, the signature's actual predicates are only evaluated
    after macro expansion and that is too late for generating the doc
    string.

    So we just stick the argument list (after uncurrying) as a line at the
    top.

commit 8aa5e3c7392cc29515c55d57a0bf0e6da8dc03ce
Author: David Kastrup <address@hidden>
Date:   Sat Sep 20 19:57:38 2014 +0200

    Issue 4121/1: Store music function argument list names in docstring

    For one thing, the doc string does not make a lot of sense without the
    argument list and it cannot reliably be deduced from the doc string
    itself.

    For another, GUILEv2 does not do us the favor of storing the original
    argument list anywhere where it could be retrieved with a useful amount
    of labor.

    While it would be nice to put the types of the arguments into the doc
    string as well, the signature's actual predicates are only evaluated
    after macro expansion and that is too late for generating the doc
    string.

    So we just stick the argument list (after uncurrying) as a line at the
    top.


--
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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]