Undefined behaviour in C [was Re: The Cost of Dynamism]
Paul Rubin
no.email at nospam.invalid
Fri Mar 25 22:59:23 EDT 2016
More information about the Python-list mailing list
Fri Mar 25 22:59:23 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 ]
Steven D'Aprano <steve at pearwood.info> writes: > Culturally, C compiler writers have a preference for using undefined > behaviour to allow optimizations, even if it means changing the semantics > of your code. If your code has UB then by definition it has no semantics to change. Code with UB has no meaning.
- 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