(interesting) Simple solution to the peoblem of the copula? –“We can clarify a

(interesting)
Simple solution to the peoblem of the copula?

–“We can clarify a lot of this confusion by simply referring to “=“ as “gets”, i.e. an assignment operation. As such, this operation can only succeed if the left and right side operant belongs to the same class, i.e. type. Otherwise for a computer system incapable of operating under ambiguous conditions, the statement will fail to compile let alone execute.

If instead of “gets”, we choose to use the word “is”, it create a loop hole for false equivalency. “x = int(1)” then translates to “x is the integer 1”, which does not always evaluate to true, since you falsify the statement as soon as you execute “x=int(2)”.

Further more, if the operands belong to two distinct classes, especially ones that do not share enough in common such that you can type cast one into the other, using the copula “is” can create ambiguities. The statement “She is a man” constitutes such an ambiguity. Grammatically correct (the sentence parses), yet semantically false, and certainly fails the truth test. To use the programming analogy: one can not assign an instance of a type human male to a variable of type human female.

In summary, I think that not all use of “to be” leads to ambiguity and lies, but because a substantial subset of its usage does causes ambiguity through false equivalence, those of us striving to operate in truthful ways stand a better chance of success by avoiding its usage.”– Francis