Liste des Groupes | Revenir à theory |
On 6/3/2024 5:03 AM, Mikko wrote:Not of the input text but of the machine and input that the textOn 2024-05-31 15:13:02 +0000, olcott said:In other words embedded_H can simply play bingo and never halt and still correctly decide the halt status of its input?
On 5/31/2024 3:30 AM, Mikko wrote:There is no requirement to follow the pecifications by embedded_H.On 2024-05-31 01:54:52 +0000, olcott said:YES, exactly !!!
On 5/30/2024 8:37 PM, Richard Damon wrote:An UTM interpretes the string as a specification of behaviourOn 5/30/24 9:31 AM, olcott wrote:On 5/30/2024 2:40 AM, Mikko wrote:On 2024-05-30 01:15:21 +0000, olcott said:The string directly SPECIFIES behavior to a UTM or toNote, the string doesn't DIRECTLY specify behavior, but only indirectly as a description/representation of the Turing MachThat is what I said.x <is> a finite string Turing machine description that SPECIFIES behavior. The term: "representing" is inaccurate.No, x is a description of the Turing machine that specifies the behaviour
that H is required to report.
any TM based on a UTM.
and another Turing machine may interprete likewise. But in aWhen Ĥ is applied to ⟨Ĥ⟩
different context the interpretation is different.
Ĥ.q0 ⟨Ĥ⟩ ⊢* embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.qy ∞
Ĥ.q0 ⟨Ĥ⟩ ⊢* embedded_H ⟨Ĥ⟩ ⟨Ĥ⟩ ⊢* Ĥ.qn
When embedded_H <is> a UTM or <is> a halting computation based on a
UTM then the ⟨Ĥ⟩ ⟨Ĥ⟩ input to embedded_H SPECIFIES that ⟨Ĥ⟩ ⟨Ĥ⟩ correctly
simulated by embedded_H cannot possibly reach its own simulated final
state at ⟨Ĥ.qn⟩.
Les messages affichés proviennent d'usenet.