2 ms·
You don't need a separate linter for this stuff today, proper compilers (anything but MSVC basically) have the most important type-related warnings in the defau
by flohofwoe 3y ago
You don't need a separate linter for this stuff today, proper compilers (anything but MSVC basically) have the most important type-related warnings in the default warning set, and it always makes sense to bump warnings to the highest level (both in C and C++ btw) - also (because I know this will be brought up): implicit conversion of a void* to other pointer types is a feature, not a bug ;)
- pjmlp 3y agoEven enabling -Wall is a debatable point of view in some circles. VC++ is actually quite good, has SAL, /analyse and SFIR. Also much better than many other compilers, when looking beyond the big three. Implicit conversations is a common source of errors. Certainly a nice feature for pentesting.
- flohofwoe 3y agoMSVC is almost completely silent with the default warning level though, both in C and C++ mode, at least from my experience (it might have gotten better in very recent versions, I wouldn't have noticed since first thing I do is bump the warning level to /W4 anyway).