Welcome to Code Forum!

Join a community that supports you and your coding journey from day one. We strive to be a friendly, supportive community that empowers everyone to be better developers. By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!
  • Guest, before posting your code please take these rules into consideration:
    • It is required to use our BBCode feature to display your code. While within the editor click < / > or >_ and place your code within the BB Code prompt. This helps others with finding a solution by making it easier to read and easier to copy.
    • You can also use markdown to share your code. When using markdown your code will be automatically converted to BBCode. For help with markdown check out the markdown guide.
    • Don't share a wall of code. All we want is the problem area, the code related to your issue.

    GIF shows where to locate </> in the thread and or post editor toolbar.
    To learn more about how to use our BBCode feature, review our "How to post your code into threads" here.

    Thank you, Code Forum.

Requiring the logically impossible is always an invalid requirement

polcott

Active Coder
It is logically impossible to draw a square circle because it
must be perfectly round AND not round at all with four equal
length sides.

It is clear that the impossibility of creating a CAD system that
can correctly draw square circles places no limits on what
computers can do.

It is less clear that requiring a program H to report on the behavior
of another program D that does the opposite of whatever H says
is a logical impossibility when we see that program H1 can correctly
say what D will do.

When we get back to the original {halting problem} we can see
that no program H can ever always say what every program
D will do because some D will do the opposite of whatever H says.

So the when the {halting problem} requires a program H to always
say whatever program D will do includes programs that do the
opposite of whatever H says this is requiring the logically impossible,
thus the same as requiring a CAD system to correctly draw square circles.

The {halting problem} as defined requires the logically impossible
therefore it places no actual limits on what can be computed.

This above is based on my own work since 2004 that did not become
clear enough to understand until I discussed this with Professor Hehner
based on his equivalent ideas.


Objective and Subjective Specifications
Professor Rick Hehner PhD (2017)
 
Last edited:
These verbatim words were approved by
computer science Professor Rick Hehner PhD:


The gist of the issue with the halting problem seems to be
that the whole notion of decision problem undecidability is
inherently flawed in that it requires the logically impossible.

Requiring a halt decider H to report on the behavior of the
direct execution of input D when D has been defined to do
the opposite of whatever Boolean value that H returns is
simply an incorrect problem definition because it requires
the logically impossible.
 
Last edited:

Buy us a coffee!

Buy me a coffee.
Back
Top Bottom