----------------------------------------------------------------------------------
@MSGID: SuUf.78694@fx14.iad>
440c204a
@REPLY: 3@dont-email.me> 2682d15f
@REPLYADDR Richard Damon
<Richard@Damon-Family.org>
@REPLYTO 2:5075/128 Richard Damon
@CHRS: CP866 2
@RFC: 1 0
@RFC-References: 3@dont-email.me>
1@dont-email.me> 1@dont-email.me> 1@dont-email.me>
1@dont-email.me> 1@dont-email.me> 1@dont-email.me>
1@dont-email.me> 1@dont-email.me> 2@dont-email.me>
1@dont-email.me> 1@dont-email.me> 1@dont-email.me>
1@dont-email.me> 1@dont-email.me> 1@dont-email.me>
3@dont-email.me>
@RFC-Message-ID:
SuUf.78694@fx14.iad>
@TZUTC: -0400
@PID: Mozilla Thunderbird
@TID: FIDOGATE-5.12-ge4e8b94
On 8/18/23 1:08 PM, olcott wrote:
> On 8/18/2023 12:03 PM, Mikko wrote:
>> On 2023-08-18 15:48:09 +0000, olcott said:
>>
>>> The behavior of D(D) directly executed in main() does *NOT*
>>> provide the behavior of the actual input to H(D,D).
>>
>> Of course not. The actual input to H(D,D) is just a text string
>> that has no behaviour. It can be interpreted to specify a behaviour
>> but it iself does not behave.
>>
>> The actual behaviour of D(D) is merely a reference for determination
>> of the orrectness of the answer given by H(D,D).
>>
>> Mikko
>>
>
> The notion of a UTM proves that D correctly simulated by H does provide
> the behavior that H must report on.
>
The notion of a UTM says that the "Correct Simulation" of an input
exactly matches the behavior of the machine the input describes.
Thus, your H does NOT do a "Correct Simulation", since you claim that
H`s simulation doesn`t (or doesn`t need to) match the behavior of the
actual machine described by the input.
Since you claim:
>>> The behavior of D(D) directly executed in main() does *NOT*
>>> provide the behavior of the actual input to H(D,D).
Then H is NOT actually a Halt Decider, as a Halt Decider DOES look at
the bevhaior of the machine described by its input, an not some other
processing that it does on it.
--- Mozilla Thunderbird
* Origin: Forte - www.forteinc.com (2:5075/128)
SEEN-BY: 5001/100 5015/255 5019/40 5020/715 848
1042 4441 12000 5030/49 1081
SEEN-BY: 5058/104 5075/128
@PATH: 5075/128 5020/1042 4441