DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2481 Version: 1.3.0 I've been seeing those for ages. I looked into it once, and it's kinda complicated to solve. The issue, IIRC, is these are static functions and data defined in files that actually get #included, defining the static data in each module that includes it. But these modules might not use all the functions defined in them. This is kind of an 'abuse' of #include files to define static code used inline in other modules. For instance, one include file defines two static functions; xxx_mbtowc and xxx_wctomb. Another module then #include's that file, but only calls the xxx_wctomb function, not the other one, which becomes dead code, so the compiler complains. The compiler is kinda right to complain that a static function defined but not called in the module is essentially dead code. Still, I can see where it's maybe best not to create a complex set of #ifdefs just to silence these warnings.. That's my take on it. Maybe Albrecht or one of the UTF8 devs has an opinion on this. Link: http://www.fltk.org/str.php?L2481 Version: 1.3.0 _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
