Random832 random832 at fastmail.com
Fri Mar 25 22:56:51 EDT 2016

• Previous message (by thread): Undefined behaviour in C [was Re: The Cost of Dynamism]
• Next message (by thread): Undefined behaviour in C [was Re: The Cost of Dynamism]
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Fri, Mar 25, 2016, at 22:46, Steven D'Aprano wrote:
> Culturally, C compiler writers have a preference for using undefined
> behaviour to allow optimizations, even if it means changing the semantics
> of your code. The C compiler is allowed to ignore your code, move it
> around
> so that things happen in a different order, or add its own code, even if
> that changes the semantics of the code.

Er, the point of undefined behavior is that your code doesn't *have*
semantics.

---

• Previous message (by thread): Undefined behaviour in C [was Re: The Cost of Dynamism]
• Next message (by thread): Undefined behaviour in C [was Re: The Cost of Dynamism]
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-list mailing list