Karlin High <karlinh...@gmail.com> writes:
> On Tue, Apr 24, 2018 at 9:18 AM, Robert Hickman <robehick...@gmail.com> wrote:
>> The only way to create good documentation is to listen to your users
>> problems and progressively make improvements.
>
> Yes, exactly! The LilyPond community has a process for this.
> <http://lilypond.org/doc/v2.19/Documentation/contributor/documentation-suggestions>
>
> However, in any software development community, some suggestions are
> more likely to be accepted than others. For example, if I went to a
> forum for a C-family language and said "This whole business of ending
> each line with a semicolon is just stupid; you need to change that!"
> what response would I get? Swift and overwhelmingly negative, right?
Uh, no? There is a reason
#define BLA(...) do { ... } while (0)
is an idiom. Exactly in order _not_ to end with a semicolon when doing
if (...)
BLA (xxx);
else
blubb ();
> That language element was settled years ago, and my opinions on it are
> irrelevant. Whatever help I would get from the C-people, getting rid
> of the semicolons would not be part of it.
Except when it's a clever way of getting rid of an unwanted semicolon.
Or in this case, create a semicolon hole, a negative semicolon count.
Add one semicolon, and none remains.
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
