Liste des Groupes | Revenir à c theory |
On 5/17/24 11:35 PM, olcott wrote:You have not shown that.On 5/17/2024 9:40 PM, Richard Damon wrote:And create a contradiction.On 5/17/24 10:19 PM, olcott wrote:>On 5/17/2024 8:33 PM, Richard Damon wrote:>On 5/17/24 9:22 PM, olcott wrote:>On 5/17/2024 8:07 PM, Richard Damon wrote:>>>>
On 5/13/2024 7:29 PM, Richard Damon wrote:
> Remember, p defined as ~True(L, p) ...
>
You already admitted that True(L,p) and False(L,p) both return false.
This is the correct value that these predicates correctly derived.
Right, but that also means that we can show that True(L, true) returns false, which says your logic system is broken by being inconsistant.
>
Not at all. Your version of the Truth Teller paradox has
the conventional lack of a truth object as the Liar Paradox
and the Truth Teller paradox: What are they true about?
In other words, you logic doesn't have an absolute idea of truth!!!
>
It does have an immutably correct notion of {true on the basis
of meaning} and rejects finite strings as not truth bearers on
this basis.
Nope, because you said the value of "true" doesn't exist, truth is dependent on having something to make true.
>
True(L,x) is defined in terms of its truthmaker.
This seems to indicate that when on non truth-bearer such as "a fish"A whole bunch of expressions are stipulated to have the semanticand everything derivable from them with truth preserving operations, including the defined behavior of the True operator, and thus,
property of Boolean true. Being a member of this sat is what makes
them true.
p is not a truth-bearer thus behaves the exact same way as any>p is true, because True(L, p) being false made it so, since p was defined to be ~True(L, p)>>>The object that made the statement true, was that True(L, p) said that p wasn't true.>
>
*You agreed that True(L, p) is false and False(L,p) is false*
*You agreed that True(L, p) is false and False(L,p) is false*
*You agreed that True(L, p) is false and False(L,p) is false*
Yes, which makes True(L, a sentence proven to be true) to be false.
>
Thus, it is inconsistant.
>
*It has nothing that it is true about so it is not true*
*It has nothing that it is true about so it is not true*
*It has nothing that it is true about so it is not true*
THIS is the "true" that True(L, p) has previously defined to be false,We cannot correctly say it that way because we a leaving
and thus your True predicate is shown to be inconsistant.It is not inconsistent and you have only shown your own lack
I simply applied the same reasoning that you applied to>Why?Or we can use the arguement that since>
>
p is ~True(L, p) which is false that p is alse
then "a fish" because ~True(English, "a fish") is false that
makes "a fish" false.
True didn't make p true because it was an input to the Truth Predicate, but because p was defined as an expression based on it,p = "a fish"
where was this done to "a fish".
You are just proving you don't understand what is being talked about.*I AM NOT SURE IF YOU FULLY UNDERSTAND THIS*
>In other words, you logic doesn't understand how to handle references!~True(L, ~True(L, p) which, since True(L, p) is "established" to be false, and thus ~True(L,p) to be true, we can say that True(L, ~True(L, p) must be true>
*ONE LEVEL OF INDIRECT REFERENCE CHANGES EVERYTHING*
*ONE LEVEL OF INDIRECT REFERENCE CHANGES EVERYTHING*
*ONE LEVEL OF INDIRECT REFERENCE CHANGES EVERYTHING*
Note, p is different than a statement that SAYS something about a sentence it mentions, p is defined by a predicate applied to a sentence (that happens to be itself).Forming an infinite evaluation cycle that is rejected by Prolog using:
By using the same incorrect reasoning that you applied to p>How do you "prove" "a fish" to be true and false?and thus p, being not that is false.>
>
So, we can prove that p is both false and true, and thus your system is BY DEFINITION inconsistant.
>
We can prove that p is both false and true the exact same way
and to the exact same degree that "a fish" is both true and false.
By your definitions it is neither.Likewise for p
That is the difference between the statement p and a sentence that is trivially a non-truth-bearer (one that doesn't state something).TT := "This sentence is true"
Not true and your every attempt to show this had glaring errors.>Then so is your "predicate True".
<snip>
>>*No you said this* (Socratic question)>
No, YOU said it first, and I agreed.
>
What else are you going to make it?
>
(Socratic reply question)
>>>thus the truth value of p MUST be true, since it is not the falseness of True(L, p)>
>
We test p for True or False if neither it is tossed out on its ass.
>
It is like we are testing if a person is hungry:
We ask is the person dead? The answer is yes and then you
say what if they are still hungry?
>
RED HERRINBG.
>
p is dead!
Every expression that is neither true nor false
is dead to any system of bivalent logic.
That is the problem you face, since p is DEFINED BY True, for p to be "dead", so must the idea of the existance of the predicate "True"TT := True(TT)
The exact same way that "a fish" is not a truth-bearer>Right, which by your definition means that p can not be true.Since you have claimed that True(L, p) is false, by the stipulated definition of p,>
Nope I never said that. You agreed that
>
There are no sequence of true preserving operations applied to
expressions that are stipulated to be true that derive p or ~p.
You have never shown this.>No, your system contradicts itself.
Likewise for "a fish",
"this sentence is not true" and
"this sentence is true".
>it MUST be a true statement, and thus you have>
Then you contradict yourself when you said
>> On 5/13/2024 7:29 PM, Richard Damon wrote:
> No, so True(L, p) is false
you system says that since, at least initially, we can not find a path to p or ~p, True(L, p) must be false.Likewise when we try a quadrillion different times
But once we have the decision, we now have a path that makes p true, and thus True is forced into a contradiction.*If we did then we could make "a fish" true*
(a) A set of finite string semantic meanings that form an accurate>FALSE. Formal Logic has NOTHING to do about the actual world, but about the stipulations (via the axioms of the system).stiplated that True(L, <a statement proven to be true>) turns out to be false (since that statement IS p), and thus you system is>
>
*Illegal stipulation. It must come from here*
(a) A set of finite string semantic meanings that form an accurate
model of the general knowledge of the actual world.
In fact, it is generally considered impossible to fully formalize the "actual world" as we would need to actually KNOW all the actual facts and relationships of the actual world.Only the facts of general knowledge of the actual world, context
Formal logic allows us to define APPROXIMATE models of the "real world", to try to deduce new things about the "real world".A {cat} is not {approximately} an {animal}
A complete and accurate model of the general knowledge of>Can't be. You don't have a complete and accurate model of the general knowledge of the actual world.Yes that one is: "This sentence is not true">Thus we can say that p is also the equivalent in L of>
>
We sure as Hell cannot correctly say that.
Why not?>>
*THE ONE LEVEL OF INDIRECT REFERENCE CHANGES EVERYTHING*
*THE ONE LEVEL OF INDIRECT REFERENCE CHANGES EVERYTHING*
*THE ONE LEVEL OF INDIRECT REFERENCE CHANGES EVERYTHING*
In other words, you system doesn't allow the assignement of a statement to have a refenece to itself, which is one of the criteria in Tarski.
>>>~True(L, ~True(L, p))>
~True(English, ~True(English, "a fish")) is true
~True(English, ~True(English, "This sentence is not true")) is true
~True(English, ~True(English, "This sentence is true")) is true
Nope, "This statment is true" is different then the statement:
>
P, in L, is defined as ~True(L, P)
>>The prior one is the ordinary Liar Paradox formalized.
It it just
>
P in L is defined as "P is not true."
>
>The difference is the statement P is not true has the possibility of being a non-truth bearer, but the predicate True(L, p) doesn't have that option.>
>
The predicate simple says True(L, p) is false and False(L,p) is false.
This is the same ESSENTIAL idea as Prolog unable to apply Rules to Facts to derive p or ~p.
>
The key difference is that my Facts are a complete and accurate model
of the general knowledge of the actual world...
And to say you system is based on that just makes your system a lie.The set of general facts that the set of minds and the set of
LP := ~True(L, LP) is simply the formalized liar paradox>Yes, but we didn't. And the string ~True(L, p) has semantic meaning.>>>>>
Which since we showed that True(L, p) was false, that means that the outer True predicate sees a true statement (since it is the negation of a false statement)
~True(English, ~True(English, "a fish")) is true
Yep.
>>>and thus True(L, ~True(L, p)) is true, and thus we can show that p must be false.>
>
By this same reasoning we can show that "a fish" must be false.
Nope, because a fish wasn't defined to be any of those sentencds.
>
"~True(L, p)" is merely a finite string input assigned to the variable named p. We could have as easily have assigned "a fish" to p.
And the semantic meaning leads to a contradiction no matter how you assign a logical value to True(L, p),Not at all its logical value is false.
Les messages affichés proviennent d'usenet.