Re: Issue 716 in lilypond: --disable-optimisation causes `Parsed object should be dead'

2008-12-28 Thread Nicolas Sceaux
Le 28 déc. 08 à 23:43, codesite-nore...@google.com a écrit : Updates: Cc: nicolas.sceaux Comment #1 on issue 716 by hanwenn: --disable-optimisation causes `Parsed object should be dead' http://code.google.com/p/lilypond/issues/detail?id=716 this was introduced between .64 and .65, I

Issue 716 in lilypond: --disable-optimisation causes `Parsed object should be dead'

2008-12-28 Thread codesite-noreply
Updates: Cc: nicolas.sceaux Comment #1 on issue 716 by hanwenn: --disable-optimisation causes `Parsed object should be dead' http://code.google.com/p/lilypond/issues/detail?id=716 this was introduced between .64 and .65, I suspect due to nic's changes for nested bookpaper. Nicolas

Issue 716 in lilypond: --disable-optimisation causes `Parsed object should be dead'

2008-12-28 Thread codesite-noreply
Status: Accepted Owner: lemzwerg Labels: Type-Defect New issue 716 by lemzwerg: --disable-optimisation causes `Parsed object should be dead' http://code.google.com/p/lilypond/issues/detail?id=716 [git 2008-12-27] Even the simplest lilypond input (like `{ c }') causes programming error: Pars