On 12/2/25 13:22, [email protected] wrote: > 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
And even more, for some constructs that emit those warnings, most of the time, they should be rewritten in a warning free manner. For the very few occurence that it is by design, there should be #pragma that can disable some warnings for a small code area. That way we have the best of every side on the coin. On Tue, Dec 2, 2025 at 7:56 PM Dave McGuire <[email protected]> wrote: > I agree, and everything I write is compiled with -Wall too, but I > think most people don't work that way. And that's one of the reasons that rust feels much safer than C. It's not only the language. It's mostly that people are accepting warnings from the rust compiler that they fight against in C. Cheers -- Steve Schnepp _______________________________________________ Sdcc-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sdcc-user
