score, so he started looking at the software, and he quickly got hooked.
It was soon decided that MPP was a dead end. After lots of
philosophizing and heated e-mail exchanges Han-Wen started LilyPond in
-1996. This time, Jan got sucked into Han-Wen's new project. The rest
-is, as they say, history.
+1996. This time, Jan got sucked into Han-Wen's new project.
+
+A stable release, like version 1.6 is a good moment to contemplate the
+past and the present. Looking back we notice something curious: when
+we started, we mistook our naivite for self confidence, and our
+interested was piqued by music typography. LilyPond was our pet
+project. Somewhere along the line, it grew out of our hands. Today, we
+can't tell whether we are doing LilyPond, or LilyPond is doing
+us. Working on it has become more than a simple hobby. We're not sure
+how this happened, but we think
+
+ overestimated our slef the combination of high energy strong
+
+
+
+ one thing that
+stands out. Somewhere
+
[TODO some more here.]
(c) 1997--2002 Han-Wen Nienhuys <hanwen@cs.uu.nl>
*/
#include <math.h> // rint
+#include <stdio.h>
#include "gourlay-breaking.hh"
#include "column-x-positions.hh"
i = prev;
}
+ if (verbose_global_b)
+ printf("Optimal demerits: %f\n", optimal_paths.top().demerits_f_);
+
+
if (optimal_paths.top ().demerits_f_ >= infinity_f)
warning (_ ("No feasible line breaking found"));
return last_grob;
}
-/*
-*/
void
Staff_spacing::get_spacing_params (Grob *me, Real * space, Real * fixed)
{
&last_ext);
if (!last_grob)
{
- programming_error ("empty break column? --fixme");
+ /*
+ we used to have a warning here, but itgenerates a lot of
+ spurious error messages.
+ */
return ;
}