On 2016-11-08 15:02, mclaren wrote:
Whatever Lilypond is doing internally, there's some arbitrary limit to
the
numbers it uses. Time signatures above some large value cause a crash.
Too
many tuplets of too many different kinds causes Lilypond to crash.
Hi mclaren,
So you found bugs in LilyPond. In fact, I can reproduce the time
signature issue in 2.19.50, since this code causes LilyPond to hang:
{
\time 9999999999/1
s1
}
You don't need to go on a whole rant about how it's stupid or unmusical,
and you don't need to accuse LilyPond of being backed by a conspiracy of
programmers out to destroy music. It's a mistake, plain and simple, and
it was overlooked because nobody has reported it before, and nobody has
reported it before because such time signatures are extremely rare. I
certainly would not expect to see them outside of "score as art" works,
such as some of Tom Johnson's graphic scores or John Stump's infamous
parody engravings.
I agree that these limitations are flaws in LilyPond that should be
fixed. Maybe if you could grow up and stop being so entitled and
accusative, the dev team would be willing to accommodate these needs,
prioritization issues notwithstanding.
Nathan
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
