Øyvind Harboe a écrit : >> -Wall is the minimum that should be applied to source code. Running it >> through Splint (or some other verification tool) would not hurt either. > > Is there an open source lint tool that's worthwhile to use? > > Did you try splint on OpenOCD?
Apart from Splint, I haven't used open source verification tools (but I do use a non-open source one in my day job). And no, I haven't tried splint on it, although I could give it a try if you want. >>> You *can* disable error on warnings at configure time. >> I personally would never turn this off, and I hate when a codebase requires >> it to be turned off because someone was not bothered enough by some warning >> to fix the root cause. There are places where the policy is "when changing >> code, verify that you dont get *more* warnings than before". :/ > > > There are legitimate uses: e.g. recompiling an *old* version with > a newer compiler can yield warnings that are fixed in latest > version of openocd. You've got a point here -- this is all the more a reason for having -Wall, in order to detect such situations as early as possible. Amicalement, -- Albert. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
