Re:C constructs that still don't work in C++
by spacechild1 on Thursday May 28, 2026 @11:15AM
(#48310160)
But you can't argue that a warning is less severe than a hard compiler error. Warnings can be supressed or ignored.
You were right to call out that the C standard only talks about diagnostics and the actual implementation is left to the compilers, but I don't think it really changes the actual argument I've been trying to make, namely that - unlike in C++ - implicit incompatible pointer casts are not a guaranteed compiler error.
You were right to call out that the C standard only talks about diagnostics and the actual implementation is left to the compilers, but I don't think it really changes the actual argument I've been trying to make, namely that - unlike in C++ - implicit incompatible pointer casts are not a guaranteed compiler error.