I wouldn't bother; output is fine.
On 7/3/07, Graham Percival <[EMAIL PROTECTED]> wrote:
No, we don't worry about programming errors. We produce too many false warning messages to bother fixing them. If it's a first-time bug reporter, I'll faithfully add it to the tracker, but they get the lowest priority. Cheers, - Graham Trevor Bača wrote: > Hi, > > Do we need to worry about this programming error? I was interpreting a > gigantic inputfile (65,000 lines) but the output turned out just fine. > > Here's the complete output of the run (which is quite clean except for > the one error), running under OS X: > > GNU LilyPond 2.11.26 > Processing `1083.ly' > Parsing... > Interpreting music... [8][16][24][32][40][48][56] > Preprocessing graphical objects... > Finding the ideal number of pages... > Fitting music on 55 or 56 pages... > Drawing systems... > Layout output to `1083.ps'... > Converting to `1083.pdf'... > programming error: Parsed object should be dead: static > scm_unused_struct* Prob::mark_smob(scm_unused_struct*) > continuing, cross fingers > > > I can send over the complete inputfile if anyone cares; but, again, > the output is just fine. > > > ------------------------------------------------------------------------ > > _______________________________________________ > bug-lilypond mailing list > bug-lilypond@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-lilypond >
-- Trevor Bača [EMAIL PROTECTED]
_______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond