Semiconductor & Computer Engineering
From WikiChip
Editing nasal demons
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.
| Latest revision | Your text | ||
| Line 2: | Line 2: | ||
The term originally originated from a post by ''John F. Woods'' on 2/25/92 in a discussion on the Usenet group comp.std.c<ref>[https://groups.google.com/forum/?hl=en#!msg/comp.std.c/ycpVKxTZkgw/S2hHdTbv4d8J The original post by John Woods] 2/25/92</ref>. Mr Woods was attempting to emphasis the fact that [[undefined behavior]] may legally (as far as the standard is concerned) result in the compiler doing just about anything - including but not limited to "having demons fly out of your nose". The aim of the post was to make the point that one cannot put the compiler at fault for input which has no defined behavior as far as the {{C|C89|c standard}} is concerned. | The term originally originated from a post by ''John F. Woods'' on 2/25/92 in a discussion on the Usenet group comp.std.c<ref>[https://groups.google.com/forum/?hl=en#!msg/comp.std.c/ycpVKxTZkgw/S2hHdTbv4d8J The original post by John Woods] 2/25/92</ref>. Mr Woods was attempting to emphasis the fact that [[undefined behavior]] may legally (as far as the standard is concerned) result in the compiler doing just about anything - including but not limited to "having demons fly out of your nose". The aim of the post was to make the point that one cannot put the compiler at fault for input which has no defined behavior as far as the {{C|C89|c standard}} is concerned. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== References == | == References == | ||
{{reflist}} | {{reflist}} | ||
| − | |||
| − | |||