Hi, Just for the record on the list, most of the IM warning are in the third party libraries. Other warnings I did not find any critical. Thanks for the post anyway.
Best, Scuri Em ter., 21 de jan. de 2020 às 01:55, sur-behoffski < sur_behoff...@grouse.com.au> escreveu: > G'day, > > Some time ago (perhaps 1-2 years?), I was building the Tecgraf tools > suite (IM, CD and IUP), gathering the output into a file, and then > try to report warnings by category. > > This came about because I've been in several work environments where > a warning was considered an error, and I note that Gerard Holzmann > in his "Mars code" presentation, use automated/static analysers > extensively to come up with over 3 million lines of code that worked > when the mission was deployed [there were far too many lines of code > to use traditional manual code-review/software inspection processes.] > > > https://www.usenix.org/conference/hotdep12/workshop-program/presentation/Holzmann > https://www.youtube.com/watch?v=16dQLBgOwbE > > The other thing is that compilers, especially GCC on the > GNU/Linux platforms, have steadily become more proficient at > code analysis, flow analysis, and adding warnings for constructs > that had, in some cases, lead to a defect in the code (the Apple > "goto Fail;" is the classic one here). > > So, I've written a tool to take GCC output ("parse-build.lua"), > and report warnings by category. > > IM has not changed much over time, but I'm posting it now anyway > as the start of a trio of postings. > > cheers, > > sur-behoffski (Brenton Hoff) > programmer, Grouse Software > _______________________________________________ > Iup-users mailing list > Iup-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/iup-users >
_______________________________________________ Iup-users mailing list Iup-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iup-users
