Hmm, thanks for the pointer. Still costs a fortune, but at least there is something available if we'll really need it. The valgrind stuff seems to address a completly different set of programming errors, I don't think it can completly replace static source code analysis.
Oded Arbel wrote:
ביום ראשון 16 נובמבר 2003, 15:42, נכתב על ידי [EMAIL PROTECTED]:
So take this response and one negative-ack. I'd be glad to hear otherwise.
Anyone can recommend or warn against usage of a (preferably Open Source, otherwise customizable) lint-like tool, for static checking of C++ and/or C# code?
Me and a friend have looked such a thing up and down the net for quite a while but so far haven't found anything. The only thing we found that gives such a funcionality is PC-Lint for windows, which is proprietary (and saved my previous workplace its money's worth tenfold in amount of work time).
There is something called FlexeLint which supposed to be a PC-Lint port which is distributed in source form (obfuscated, or so they say) and compilable on most platforms. Linux is specifically mentioned.
BTW - what about dynamic checking, i.e. valgrind ?
P.S. Sorry for the double post
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
