On Mon, Feb 27, 2012 at 02:12:06AM +0100, David Kastrup wrote: > Colin Hall <[email protected]> writes: > > > On Sun, Feb 26, 2012 at 06:36:05PM +0100, Thomas Morley wrote: > >> The following code gives a log warning: > >> > >> \version "2.15.30" > >> \new Staff { > >> \set tupletFullLength = ##t > >> % \override TupletBracket #'full-length-to-extent = ##f > >> \time 1/8 > >> \times 2/3 { c'16 c' c' } > >> \mark "123456789" > >> } > >> > >> log: > >> warning: Found infinity or nan in output. Substituting 0.0 > >> > >> If the mark contains less than 8 characters the warning disappears. > >> Same, when commenting in \override TupletBracket #'full-length-to-extent = > >> ##f > >> > >> Compiles without warning using 2.12.3 > >> > > > > Thanks for the bug report, Thomas, but I'm not sure that I should > > create an issue tracker for this. > > > > As far as I can tell you are reporting that 2.15.30 gives a warning > > and 2.12.3 does not. > > > > Do 2.15.30 and 2.12.3 both give good typeset output? > > > > In that case, I think the difference in behaviour is not a bug, but > > just a change in the way the software handles a particular case. > > > > Anyone from bug squad or dev care to comment? > > The warning describes a problem with data generated internally, not a > problem with the user input. This is definitely a bug. It is not > necessarily a regression since it is conceivable that 2.12.3 just did > not diagnose the problematic situation. So it will require some > analysis by a developer to decide whether this is also a regression.
Thanks for the prompt feedback, David and Graham. I'll enter it as a bug. Cheers, Colin. -- Colin Hall _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
