Updates:
Status: Fixed
Labels: -Patch-review
Comment #13 on issue 804 by k-ohara5...@oco.net: Code cleaning: checking
types-conversion issues and other build warnings
http://code.google.com/p/lilypond/issues/detail?id=804
Lexer warnings resolved with commit da949cdc
On 32-bit systems, Lilypond now compiles with only *one* warning, fromb
auto-generated code produced by GNU Bison.
We /could/ remove that last warning with "#define YYTYPE_INT16 int" in our
parser.yy. This would make the parser-state stack, and a couple other
modestly-sized arrays, comprise ints instead of 16-bit ints. I am mildly
of the opinion that it is better to leave the warning.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
