Is the following truth table the definition of the conditional?
What is the motivation for this definition? Is it defined this way just so that the definition for a biconditional works out in a desired way?
When others have tried to explain it to me, they have told me to think of the conditional as a promise. The reasoning makes sense for the two cases where p is true. However a typical line of reasoning when p is false goes like this: "If p is false, q can be true or false and it won't break the promise. Therefore the promise is still true."
1. I'm not sure if thinking of it as a promise is even appropriate. Saying the promise is still true, implies we know it was true before.
2. Just because the promise is not false, would not make it true. Just as we don't have enough information to call it false, we don't have enough information to call it true.
Code:
p q p-->q
T T T
T F F
F T T
F F T
What is the motivation for this definition? Is it defined this way just so that the definition for a biconditional works out in a desired way?
When others have tried to explain it to me, they have told me to think of the conditional as a promise. The reasoning makes sense for the two cases where p is true. However a typical line of reasoning when p is false goes like this: "If p is false, q can be true or false and it won't break the promise. Therefore the promise is still true."
1. I'm not sure if thinking of it as a promise is even appropriate. Saying the promise is still true, implies we know it was true before.
2. Just because the promise is not false, would not make it true. Just as we don't have enough information to call it false, we don't have enough information to call it true.