Hello Michiel,

On Fri Dec 23 2016 15:46:00, Michiel van der Vlist wrote to Nicholas Boel:

 NB>> Why? The point was that the last time I compiled, those warnings
 NB>> weren't there. Since there were some recent updates to the code,
 NB>> I decided to compile again and report the massive amounts of
 NB>> warnings, in case someone wants to fix them.

 MV> My experience with C is that - depenndig on compiler - it is unwise to
 MV> just ignore compiler warnings. Especially with the Borland compiler
 MV> they should be taken seriously, they may point to a serious problem.

 MV> Just my Γé¼0.02,.

I agree. If they're not there before the code was modified, and then they're
there (in abundance, mind you) afterwards, I would think it's better to let
someone know it's happening at the very least - and not just ignore them
because it finished compiling. *shrug*

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20161221
 * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)