On Sun, May 02, 2010 at 11:09:32PM +0200, Joakim Tjernlund wrote:
Then the only warning left is the one fixed with #define YY_FATAL_ERROR(msg) do {cf_error(msg); if(0) yy_fatal_error(msg); } while(0) Not ideal, but the try convincing flex of that :)
This is ugly and unnecessary workaround, i would rather keep this warning.
Well, it is a defect in flex, not likely to be fixed anytime soon, and the only remaining warning in the build. Would it not be good to remove that one too, even if it is somewhat ugly? Then one would start to pay attention to all warnings as there is normally no warnings.
I usually pay attention to new warnings even if there are some small number of old unimportant 'persistent' warnings like these from flex output.
BTW, it seems like you git server is down?
Yes, we will check that. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."