[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 380 in lilypond: cycling markup reference segfaults
From: |
codesite-noreply |
Subject: |
Issue 380 in lilypond: cycling markup reference segfaults |
Date: |
Wed, 22 Aug 2007 19:41:34 -0700 |
Issue 380: cycling markup reference segfaults
http://code.google.com/p/lilypond/issues/detail?id=380
Comment #8 by gpermus:
Ugly hack:
whenever you use foo = \fromproperty #'bar, you add "foo, bar" to a global list
of
"references used". Whenever you see a \fromproperty #'baz, you check to see if
"baz"
is mentioned in the global list of references used. If it is, exit with an
error.
You probably only need to store one of foo/bar, though. I'd need to work it
out on
paper to figure out which one, though. (I do all my math with a pencil :)
I'm not proposing this as a serious suggestion, though. This is too ugly, and
IMO
not worth the trouble. If somebody is playing with \fromproperty, then they
should
be able to fix their own ly files to avoid these crashes.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
- Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 2007/08/18
- Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 2007/08/21
- Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 2007/08/21
- Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 2007/08/22
- Issue 380 in lilypond: cycling markup reference segfaults,
codesite-noreply <=
- Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 2007/08/23
- Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 2007/08/23
- Issue 380 in lilypond: cycling markup reference segfaults, codesite-noreply, 2007/08/23