Re: Constraints on a program that calls an SHD on itself

On 6/1/25 4:28 AM, Mr Flibble wrote:

Constraints on a program that calls an SHD on itself
----------------------------------------------------
 If DDD calls HHH than it is a requirement that DDD must always be
simulated by HHH and never run independently as doing so would be a type
violation.
 /Flibble

And how do you know that a given HHH that a program is calling actualy *IS* a SHD.
And why should running a program that calls another function suddenly become a "type violation".
It seems, your type rule makes SHDs themselves a Type Violation, as the major category they are part of is a "Halt Decider", and the requirements of programs of the category Hald Decider, is that their input is the representation of a program that can be run.
So, if we can't run the program the input to a SHD, then SHD themselves are just a type error, as they meaning has disappeared.