This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools.

---1463811718-1330329680-1580755187=:215607 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT

Hello,

On Mon, 3 Feb 2020, hyc@symas.com wrote:

No. The POSIX spec is *not* a part of the C spec - yet it is still valid.

POSIX spec *is* a C standard that exists in addition to the ISO C standard. ISO C defines the so-called "basic language and features" of C if you can call it that.

Which simply proves the point that just because something is not defined in the C spec does not make it invalid. The compiler guys are idiots for taking this position.

Like Jeff already said, wrongly aligned object access *is* defined by the ISO C specification. It is wrong and explicitly defined as Undefined Behaviour. Invoking UB is playing with fire, and calling compiler writers with offending names does not change that fact at all.

Spending long time on comp.lang.c should be mandatory for all C programmers out there. It is shocking to invoke UB and not bother to fix it, instead blaming compiler writers and C standard writers.

Best regards, Jokke Hämäläinen ---1463811718-1330329680-1580755187=:215607--