• Re: Two computer science professors agree with Flibble

    From Mikko@21:1/5 to olcott on Mon May 5 11:04:11 2025
    On 2025-05-05 03:10:06 +0000, olcott said:

    On 5/4/2025 10:00 PM, dbush wrote:
    On 5/4/2025 9:38 PM, olcott wrote:
    On 5/4/2025 8:13 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 04/05/2025 23:34, Mr Flibble wrote:
    The function is neither computable nor incomputable because there is no >>>>>> function at all, just a category error.

    It's a point of view.

    It's a point of view only in the sense that there is no opinion so daft >>>> that it's not someone's point of view.  The technical-sounding waffle >>>> about it being a "category error" is simply addressed by asking where
    the supposed category error is in other perfectly straightforward
    undecidable problems.  For example, whether or not a context-free
    grammar is ambiguous or not, or the very simple to pose Post
    correspondence problem.


    Flibble IS CORRECT when the halting problem is defined
    to be isomorphic (AKA analogous) to the Liar Paradox:
    "This sentence is not true".

    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports
    then both Boolean return values are incorrect

    False.  One value is correct and one is incorrect.

    Both Boolean RETURN VALUES FROM H *ARE* INCORRECT,
    Even though D halts or fails to halt.

    If D halts or fails to halt then one value is correct and
    the other value is incorrect. If D doesn't then we may
    ask "are you sure".

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Mon May 5 10:59:55 2025
    On 2025-05-05 01:38:30 +0000, olcott said:

    On 5/4/2025 8:13 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 04/05/2025 23:34, Mr Flibble wrote:
    The function is neither computable nor incomputable because there is no >>>> function at all, just a category error.

    It's a point of view.

    It's a point of view only in the sense that there is no opinion so daft
    that it's not someone's point of view. The technical-sounding waffle
    about it being a "category error" is simply addressed by asking where
    the supposed category error is in other perfectly straightforward
    undecidable problems. For example, whether or not a context-free
    grammar is ambiguous or not, or the very simple to pose Post
    correspondence problem.

    Flibble IS CORRECT when the halting problem is defined
    to be isomorphic (AKA analogous) to the Liar Paradox:
    "This sentence is not true".

    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports
    then both Boolean return values are incorrect proving
    that this form of the Halting Problem has an incoherent
    specification.

    Computer Science professor Eric Hehner PhD agrees
    in one of his many papers on the Halting Problem. https://www.cs.toronto.edu/~hehner/halting.html

    Here is another paper by another computer science
    professor that most directly agrees with Flibble:

    Even professors can say stupid things. It is best to avoid publishers
    that publish articles were anyone says anything really stupid. With
    conferences it does not matter because there the audience can spot
    and point out the stupidity.

    One should also be careful with scools that hire professors that say
    stupid things.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Mon May 5 11:09:50 2025
    On 2025-05-05 03:10:06 +0000, olcott said:

    On 5/4/2025 10:00 PM, dbush wrote:
    On 5/4/2025 9:38 PM, olcott wrote:
    On 5/4/2025 8:13 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 04/05/2025 23:34, Mr Flibble wrote:
    The function is neither computable nor incomputable because there is no >>>>>> function at all, just a category error.

    It's a point of view.

    It's a point of view only in the sense that there is no opinion so daft >>>> that it's not someone's point of view.  The technical-sounding waffle >>>> about it being a "category error" is simply addressed by asking where
    the supposed category error is in other perfectly straightforward
    undecidable problems.  For example, whether or not a context-free
    grammar is ambiguous or not, or the very simple to pose Post
    correspondence problem.


    Flibble IS CORRECT when the halting problem is defined
    to be isomorphic (AKA analogous) to the Liar Paradox:
    "This sentence is not true".

    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports
    then both Boolean return values are incorrect

    False.  One value is correct and one is incorrect.

    Both Boolean RETURN VALUES FROM H *ARE* INCORRECT,
    Even though D halts or fails to halt.

    False. If H does not return the correct value then a value that
    H does not return is correct.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mikko@21:1/5 to olcott on Mon May 5 11:13:51 2025
    On 2025-05-05 03:46:18 +0000, olcott said:

    On 5/4/2025 10:40 PM, dbush wrote:
    On 5/4/2025 11:35 PM, olcott wrote:
    On 5/4/2025 10:18 PM, dbush wrote:
    On 5/4/2025 11:10 PM, olcott wrote:
    On 5/4/2025 10:00 PM, dbush wrote:
    On 5/4/2025 9:38 PM, olcott wrote:
    On 5/4/2025 8:13 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 04/05/2025 23:34, Mr Flibble wrote:
    The function is neither computable nor incomputable because there is no
    function at all, just a category error.

    It's a point of view.

    It's a point of view only in the sense that there is no opinion so daft
    that it's not someone's point of view.  The technical-sounding waffle >>>>>>>> about it being a "category error" is simply addressed by asking where >>>>>>>> the supposed category error is in other perfectly straightforward >>>>>>>> undecidable problems.  For example, whether or not a context-free >>>>>>>> grammar is ambiguous or not, or the very simple to pose Post
    correspondence problem.


    Flibble IS CORRECT when the halting problem is defined
    to be isomorphic (AKA analogous) to the Liar Paradox:
    "This sentence is not true".

    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports
    then both Boolean return values are incorrect

    False.  One value is correct and one is incorrect.


    Both Boolean RETURN VALUES FROM H *ARE* INCORRECT,
    Category error.  Algorithms do one thing and one thing only.  And the >>>> algorithm that is the fixed code of the function H and everything it
    calls gives the wrong answer, and the opposing answer is the right
    answer.

    Look at the paper from the PhD computer science
    professor.

    Halting misconceived?
    Bill Stoddart
    August 25, 2017

    *the halting function, as described, cannot be implemented*,
    *because its specication is inconsistent*...

    *Context*
    That halting is not in general computable has been
    proved in many text books and taught on many computer
    science courses, and is supposed to illustrate the
    limits of computation. However, there is a dissenting
    view that these proofs are misconceived.

    In this paper we look at what is perhaps the simplest
    such proof, based on a program that interrogates its own
    halting behaviour and then decides to thwart it. This
    leads to a contradiction that is generally held to show
    that a halting function cannot be implemented.

    The dissenting view agrees with the conclusion that
    *the halting function, as described, cannot be implemented*,
    but suggests that this is *because its specication is inconsistent*
    https://www.complang.tuwien.ac.at/anton/euroforth/ef17/papers/ stoddart.pdf >>
    The only way for the specification to be inconsistent if there was an
    algorithm, i.e. a fixed immutable sequence of instructions, that
    neither halts nor not halts when executed directly.

    OK now we get down to the nuances.

    The way that meaning in language actually works
    as understood by linguistics: The context of
    who as asked a question <is> an aspect of the
    full meaning of this question.

    Linguistic meanings include a lot more than mathematical an computational meanings. Mathematical and computational meanings do not depend on who is asked.

    --
    Mikko

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Heathfield@21:1/5 to olcott on Mon May 5 09:33:33 2025
    On 05/05/2025 02:38, olcott wrote:
    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports

    But it isn't defined as any such thing. The Halting Problem is
    defined as asking whether a /program/ can be written that can,
    for any (syntactically correct) program and any input, correctly
    determine whether the submitted program halts on the given input.

    Turing showed that, if such a program could be written, it would
    lead to the absurdity that you find so unpalatably absurd.

    He correctly concludes that such a program cannot therefore be
    written, and *therefore* there are questions that it is easy to
    ask but to which a computer cannot provide an answer.

    --
    Richard Heathfield
    Email: rjh at cpax dot org dot uk
    "Usenet is a strange place" - dmr 29 July 1999
    Sig line 4 vacant - apply within

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon May 5 07:17:15 2025
    On 5/4/25 9:38 PM, olcott wrote:
    On 5/4/2025 8:13 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 04/05/2025 23:34, Mr Flibble wrote:
    The function is neither computable nor incomputable because there is no >>>> function at all, just a category error.

    It's a point of view.

    It's a point of view only in the sense that there is no opinion so daft
    that it's not someone's point of view.  The technical-sounding waffle
    about it being a "category error" is simply addressed by asking where
    the supposed category error is in other perfectly straightforward
    undecidable problems.  For example, whether or not a context-free
    grammar is ambiguous or not, or the very simple to pose Post
    correspondence problem.


    Flibble IS CORRECT when the halting problem is defined
    to be isomorphic (AKA analogous) to the Liar Paradox:
    "This sentence is not true".

    Excpet that it isn't isomoprhic to the Liar's Paradox, so your premise
    isn't true.



    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports
    then both Boolean return values are incorrect proving
    that this form of the Halting Problem has an incoherent
    specification.

    But that isn't the definition of the PROBLEM, but the definition of one
    way to construct a specific input for a decider, that was already defined.

    It isn't "both" answers that decider can give, it is the one answer that
    the decider DOES give.

    At the construction template level, where we say for any decider, you
    have that "both", but we aren't deciding on the template as an input (as
    that isn't a "progtam") but only on the actual program created by
    instancing the template on a given decider, to show that one decider is
    not correct for all inputs.


    Computer Science professor Eric Hehner PhD agrees
    in one of his many papers on the Halting Problem. https://www.cs.toronto.edu/~hehner/halting.html

    And he also doesn't understand that the decider the input was made needs
    to be a DEFINED program first, and thus the argument fails.


    Here is another paper by another computer science
    professor that most directly agrees with Flibble:

    Halting misconceived? --- Bill Stoddart --- August 25, 2017 https://www.complang.tuwien.ac.at/anton/euroforth/ef17/papers/stoddart.pdf


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Mon May 5 21:16:12 2025
    On 5/4/25 11:10 PM, olcott wrote:
    On 5/4/2025 10:00 PM, dbush wrote:
    On 5/4/2025 9:38 PM, olcott wrote:
    On 5/4/2025 8:13 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 04/05/2025 23:34, Mr Flibble wrote:
    The function is neither computable nor incomputable because there
    is no
    function at all, just a category error.

    It's a point of view.

    It's a point of view only in the sense that there is no opinion so daft >>>> that it's not someone's point of view.  The technical-sounding waffle >>>> about it being a "category error" is simply addressed by asking where
    the supposed category error is in other perfectly straightforward
    undecidable problems.  For example, whether or not a context-free
    grammar is ambiguous or not, or the very simple to pose Post
    correspondence problem.


    Flibble IS CORRECT when the halting problem is defined
    to be isomorphic (AKA analogous) to the Liar Paradox:
    "This sentence is not true".

    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports
    then both Boolean return values are incorrect

    False.  One value is correct and one is incorrect.


    Both Boolean RETURN VALUES FROM H *ARE* INCORRECT,
    Even though D halts or fails to halt.

    No, the given H can only return one of the values.

    The other one is correct.


    The linguistic context of WHO IS ASKED is an essential
    part of the question.

    No, because H^ has the same behavior to all deciders, it only makes H
    wrong, as it behaves the opposite of whichever is the one answer that H
    gives.


    Math and Comp Sci people that are clueless about these
    details of how language actually works think that they
    can get away with ignoring a crucial part of the actual
    question.

    No, you are clueless as to the requirements of H being a program / fixed algorithm.

    You can't ask the question until you choose which decider you are going
    to claim you are going to make your example correct decider,

    Then the challenger can make an input, custom taylored for THAT one
    decider that it will get wrong.

    Your problem is you don't understand that programs are not willful, but
    fully deterministic, and thus don't have choice.


    The answer given by the algorithm doing the deciding for the algorithm
    described by the input is the incorrect one.



    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue May 6 07:25:58 2025
    On 5/5/25 9:31 PM, olcott wrote:
    On 5/5/2025 8:16 PM, Richard Damon wrote:
    On 5/4/25 11:10 PM, olcott wrote:
    On 5/4/2025 10:00 PM, dbush wrote:
    On 5/4/2025 9:38 PM, olcott wrote:
    On 5/4/2025 8:13 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 04/05/2025 23:34, Mr Flibble wrote:
    The function is neither computable nor incomputable because
    there is no
    function at all, just a category error.

    It's a point of view.

    It's a point of view only in the sense that there is no opinion so >>>>>> daft
    that it's not someone's point of view.  The technical-sounding waffle >>>>>> about it being a "category error" is simply addressed by asking where >>>>>> the supposed category error is in other perfectly straightforward
    undecidable problems.  For example, whether or not a context-free >>>>>> grammar is ambiguous or not, or the very simple to pose Post
    correspondence problem.


    Flibble IS CORRECT when the halting problem is defined
    to be isomorphic (AKA analogous) to the Liar Paradox:
    "This sentence is not true".

    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports
    then both Boolean return values are incorrect

    False.  One value is correct and one is incorrect.


    Both Boolean RETURN VALUES FROM H *ARE* INCORRECT,
    Even though D halts or fails to halt.

    No, the given H can only return one of the values.

    The other one is correct.


    The linguistic context of WHO IS ASKED is an essential
    part of the question.

    No, because H^ has the same behavior to all deciders, it only makes H
    wrong, as it behaves the opposite of whichever is the one answer that
    H gives.


    Math and Comp Sci people that are clueless about these
    details of how language actually works think that they
    can get away with ignoring a crucial part of the actual
    question.

    No, you are clueless as to the requirements of H being a program /
    fixed algorithm.


    That is NOT what professor Sipser agreed to.

    <MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>
        If simulating halt decider H correctly simulates its input D
        until H correctly determines that its simulated D would never
        stop running unless aborted then

    *would never stop running unless aborted*
    is one actual input and the hypothetical
    HHH/DD that never aborts.


    But hypothetical DD isn't the DD that was given to the original HHH, and
    thuys you are just admitting that you have been lying about what was
    meant by the statement, because you are just too stupid to know what you
    are talling about.

    The input D calls a particular version of H, and to be that input, it
    can only call that version. To change it is to lie about what things are.

    Sorry, you just punched your ticket to the lake of fire.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Damon@21:1/5 to olcott on Tue May 6 22:21:00 2025
    On 5/6/25 1:37 PM, olcott wrote:
    On 5/6/2025 6:25 AM, Richard Damon wrote:
    On 5/5/25 9:31 PM, olcott wrote:
    On 5/5/2025 8:16 PM, Richard Damon wrote:
    On 5/4/25 11:10 PM, olcott wrote:
    On 5/4/2025 10:00 PM, dbush wrote:
    On 5/4/2025 9:38 PM, olcott wrote:
    On 5/4/2025 8:13 PM, Ben Bacarisse wrote:
    Richard Heathfield <rjh@cpax.org.uk> writes:

    On 04/05/2025 23:34, Mr Flibble wrote:
    The function is neither computable nor incomputable because >>>>>>>>>> there is no
    function at all, just a category error.

    It's a point of view.

    It's a point of view only in the sense that there is no opinion >>>>>>>> so daft
    that it's not someone's point of view.  The technical-sounding >>>>>>>> waffle
    about it being a "category error" is simply addressed by asking >>>>>>>> where
    the supposed category error is in other perfectly straightforward >>>>>>>> undecidable problems.  For example, whether or not a context-free >>>>>>>> grammar is ambiguous or not, or the very simple to pose Post
    correspondence problem.


    Flibble IS CORRECT when the halting problem is defined
    to be isomorphic (AKA analogous) to the Liar Paradox:
    "This sentence is not true".

    When the Halting Problem is defined as an input that
    does the opposite of whatever its decider reports
    then both Boolean return values are incorrect

    False.  One value is correct and one is incorrect.


    Both Boolean RETURN VALUES FROM H *ARE* INCORRECT,
    Even though D halts or fails to halt.

    No, the given H can only return one of the values.

    The other one is correct.


    The linguistic context of WHO IS ASKED is an essential
    part of the question.

    No, because H^ has the same behavior to all deciders, it only makes
    H wrong, as it behaves the opposite of whichever is the one answer
    that H gives.


    Math and Comp Sci people that are clueless about these
    details of how language actually works think that they
    can get away with ignoring a crucial part of the actual
    question.

    No, you are clueless as to the requirements of H being a program /
    fixed algorithm.


    That is NOT what professor Sipser agreed to.

    <MIT Professor Sipser agreed to ONLY these verbatim words 10/13/2022>
         If simulating halt decider H correctly simulates its input D
         until H correctly determines that its simulated D would never
         stop running unless aborted then

    *would never stop running unless aborted*
    is one actual input and the hypothetical
    HHH/DD that never aborts.


    But hypothetical DD isn't the DD that was given to the original HHH,

    Yet <is> the HHH/DD that professor Sipser agreed to:
    *would never stop running unless aborted*
    *would never stop running unless aborted*
    *would never stop running unless aborted*

    The above refers to an HHH that does not abort.
    The above refers to an HHH that does not abort.
    The above refers to an HHH that does not abort.


    No, H *IS* the one and only decider actually mentioned.

    D *is* the one and only program do decide on which calls that H.

    This H is allowed to abort its simulation, if it can prove that a
    CORRECT SIMULATION of that input will not reach a final state.

    If you have your H use that option, then the H that aborts is the H
    mentioned everywhere and the H that the D calls.

    Since that H doesn't do a correct simulation, you can't use what it does
    to prove the result, but can give that exact input to a hypothetical H
    that doesn't abort.

    When we look at that, because the input is still the input it always
    was, and thus still calls the H that aborts, we find that a correct
    simulation of that input will halt.

    Thus, the H that tried to use the rule to abort, finds that it didn't
    actually have the right to use it, so it made an error,

    It can't "go back in time" to remove that decision, as that is not an
    allowed finite string transformation.

    Your attempt at unsound logic just shows your utter ignorance of the
    fields you are attempting to talk about.

    You don't seem to understand that a program is what it is, and is fully defined, and thus we can't make D until you fix H, and then D if built
    fixed to THAT H, and then when you ask about changing H to something
    different, it doesn't go back in time to change those earlier decisions.

    The problem is you just can't build a D that does what you want, and
    changes itself based on the decider that is deciding it. Your attempts
    just prove you don't know what you are talking about.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)