On Tue, Aug 16, 2011 at 08:38:18PM +0200, David Kastrup wrote: > > Compile Lilypond with > -DSCM_DEBUG_TYPING_STRICTNESS=2 ... > But with the current code base, cleaning this all up is going to be a > lot of work. Not hard to do, but a lot.
I like it! It's something that's not challenging, it exposes the Frog to the general quality of our source code, it's a clear net win, but it's not urgent or anything. And it's pretty safe; as long as lilypond compiles and the regtests are ok, none of this is likely to break anything. Also, it can be done in stages -- if a Frog takes a week to fix two files, then another week to fix one file, then does nothing for a month but suddenly fixes half a dozen files, that's totally fine. It's ideal for a Frog who doesn't know how much time+effort she wants to spend. *cough* Bertrand? ;) Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
