On 12/2/25 13:22, [email protected] wrote:
> Anything the compiler can detect at compiletime should be either a >
warning or an error.
> Coming from Ada, it seems weird that the compiler does not flag >
everything it can detect at compile time. It saves so much debugging.
The danger here is when the compiler flags things which aren't
actually problems, which happens all the time in C. Then warnings
become annoying, then get turned off or ignored, which can cause real
problems to get missed at compile time.
So, there is a balance to be struck here.
I get your point. Maybe some MISRA on/off og something like that could
feasible. Whenever I do C, i check all warnings (and of course errors)
based on the assumption that there should be no woarnings. MOst of them
refer to some code construct that may need scrutinizing. Just my 2 cent
I agree, and everything I write is compiled with -Wall too, but I
think most people don't work that way.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
_______________________________________________
Sdcc-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sdcc-user
