Deutsch English Français Italiano |
<87jzjrkkmq.fsf@nosuchdomain.example.com> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson <Keith.S.Thompson+u@gmail.com> Newsgroups: comp.theory,comp.lang.c Subject: Re: Every D(D) simulated by H presents non-halting behavior to H ### Followup-To: comp.theory Date: Sat, 18 May 2024 12:03:41 -0700 Organization: None to speak of Lines: 24 Message-ID: <87jzjrkkmq.fsf@nosuchdomain.example.com> References: <v18e32$1vbql$1@dont-email.me> <v1h9eu$9faf$1@dont-email.me> <v1iqli$nsva$1@dont-email.me> <v1ln3c$vfh$1@news.muc.de> <v1s6e6$397iq$2@dont-email.me> <v1slmi$3cjtp$1@dont-email.me> <v1t8tt$3gu9t$3@dont-email.me> <v1vc8j$3jmr$1@dont-email.me> <v1vsru$7eqc$1@dont-email.me> <v21r4i$otc2$2@dont-email.me> <v22k4b$umr4$1@dont-email.me> <v24oah$1h4u3$1@dont-email.me> <v256fc$1kais$1@dont-email.me> <v27d05$25ga0$1@dont-email.me> <v2838r$29rd7$1@dont-email.me> <v2a8th$2ps09$1@dont-email.me> <v2ahqc$2qvr9$1@dont-email.me> <v2aicl$1ct7o$6@i2pn2.org> <v2al77$2s12h$1@dont-email.me> <v2am2q$1ct7o$8@i2pn2.org> <v2amt2$2sg5s$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain Injection-Date: Sat, 18 May 2024 21:03:41 +0200 (CEST) Injection-Info: dont-email.me; posting-host="9a36ccc98360bcb6fc9f801887e75987"; logging-data="3070821"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19ZtLmWVhlsDNmvSaHcDeul" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cancel-Lock: sha1:aHyDZ0SPA5ruUkohZvFVyrcIpBE= sha1:wEjdyUs/F3EVnUwQlp/nbStAuvo= Bytes: 2644 James Kuyper <jameskuyper@alumni.caltech.edu> writes: [...] > "Undefined behavior" is a piece of C jargon. You cannot understand the > meaning of the term by treating it as an ordinary English phrase: > "behavior which has no definition'. [...] > This is important, because strictly conforming code cannot > have undefined behavior. If the C standard has no definition for the > behavior of some code, it cannot be strictly conforming, even if some > other document does define the behavior. [...] It's also important to note that "strictly conforming" is a piece of C jargon. I don't know (or care) whether strict conformance is relevant to the discussion that should have stayed in comp.theory. If something in comp.theory raises a question about C, I suggest starting a new thread in comp.lang.c rather than cross-posting. Followups redirected back to comp.theory. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com void Void(void) { Void(); } /* The recursive call of the void */