Issue 380 in lilypond: cycling markup reference segfaults

[codesite-noreply]

Issue 380: cycling markup reference segfaults
http://code.google.com/p/lilypond/issues/detail?id=380

Comment #11 by lemzwerg:
In case this is done on C level I think that the penalty can be neglected.
I believe that stack checking is a must for interpreted languages like Scheme,
TeX, or troff.



-- 
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