Re: automatic documentation of type-p-name-alist

[Carl Sorensen]

On 4/21/10 12:56 AM, "Mark Polesky" <address@hidden> wrote:

> For a while, some of us have been wanting to generate the
> valid music-function type-predicates automatically.  I tried
> something but got stuck almost immediately.  I don't know if
> this is the right approach, but by adding these two scheme
> definitions just after the (set! type-p-name-alist ...)
> block in scm/lily.scm, a texinfo string is stored in the
> scheme variable "typecheck-doc-table".
> 
> For the scheme code below, I added a space after any
> double-quote that is immediately followed by an at-sign (to
> sidestep the annnoying address@hidden archive mangling).
> Though in the attached patch, I didn't add these spaces.
> Also, the columns in the table are reversed for now, since
> type-p-name-alist is sorted by predicate (not by the
> description docstring).  I'll either need to modify the
> (make-doc-typecheck-row ...) procedure so that the columns
> are switched, or reword the doc sentences leading up to the
> table (neither is a big problem).
> 
> The question is, is this the right approach?  Is there a way
> for the texinfo doc files to access the typecheck-doc-table
> string so that that the table appears as if it were inline
> texinfo?

Can you make the table in LilyPond code, instead of texinfo?  If you could,
you can put these function definitions in a .ly file, and just do
@lilypondfile{} in Documentation/notation/notation-appendices.itely.

Carl