Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.theory Subject: Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Date: Mon, 26 Oct 2020 14:26:59 -0700 Organization: None to speak of Lines: 22 Message-ID: <87d014vfto.fsf@nosuchdomain.example.com> References: <3KudnQcoffyh9AnCnZ2dnUU7-W3NnZ2d@giganews.com> <7LidnUOqhKayGQnCnZ2dnUU78THNnZ2d@brightview.co.uk> <9PadnUYvRqiLCgnCnZ2dnUU7-ePNnZ2d@giganews.com> <06qdnZHnuPfItArCnZ2dnUU7-QPNnZ2d@giganews.com> <28fef998-1b1d-40e6-a276-dfa56463ad29n@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="23bd55d66126924651ac0aa28de4ba33"; logging-data="13466"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18Ohqbw44Hm3cltvcrlgogC" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) Cancel-Lock: sha1:hlTzOTwOfbrruBViVlNrh4Z1Ujw= sha1:UVzW9Ektq841Rwh0N/HK+gZNX+g= Xref: csiph.com comp.theory:24493 Malcolm McLean writes: [...] >> You have only shown how to encode this function incorrectly: >> > It's a function. So it always behaves the same way when called with the > same arguments. That is not generally true of C functions, whose behavior can depend on data defined outside the function. Malcolm has his own meaning for the word "function", which is inconsistent with the C meaning of the word. Malcolm, please make it clear when you're using your own definition of "function", and what that definition is -- especially when C code is begin discussed. Readers of comp.theory might not be familiar with the way you use words. -- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com Working, but not speaking, for Philips Healthcare void Void(void) { Void(); } /* The recursive call of the void */