[Top][All Lists]

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

Re: [Scheme coding] turning a list into a markup/string

From: David Kastrup
Subject: Re: [Scheme coding] turning a list into a markup/string
Date: Tue, 21 Jan 2020 23:46:43 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Thomas Morley <address@hidden> writes:

> Am Di., 21. Jan. 2020 um 23:13 Uhr schrieb David Kastrup <address@hidden>:
>> Thomas Morley <address@hidden> writes:
>> > David, you remember my suggestion to generate that "General Code
>> > Reference" with an Index ... ?
>> Yes, that may have helped.  But it may also have delivered a haystack.
>> I think we probably need a "good programming" corpus, but the snippets
>> are supposed to be that.  Navigating them still is too hard.
> If you think of the "Snippets Manual" or the LSR, then I doubt they
> are best suited to what I think we need.
> Their snippets are too much targeted at delivering ready to use tools
> for actual typesetting work.
> As an example:
> music-map has the problem that you can't really stop it recursing
> deeper. One reason why you wrote map-some-music and for-some-music.
> Alas, I always need to get to their doc-strings again, to understand
> the differences and which one to use for which case.

Like in Scheme, map returns something, for doesn't.  I think that early
designs had more arguments, requiring even more doc-string lookup to get
them right.

David Kastrup

reply via email to

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