FALSE
False
"P and not P" is always false. If P is true, not P is false; if P is false, not P is true. In either case, combining a true and a false with the AND operator gives you false. And if you look at the truth table for the implication (the "therefore" part), when the left part is false, the result is always true.
FALSE.... cuz in && operator the compiler chk both of the expression if any of the expression is false then answer will be false.. for true result both of d expression must be true... by warrior2pnk
Let's take an example.If it is raining (then) the match will be cancelled.A conditional statement is false if and only if the antecedent (it is raining) is true and the consequent (the match will be cancelled) is false. Thus the sample statement will be false if and only if it is raining but the match still goes ahead.By convention, if the antecedent is false (if it isn't raining) then the statement as a whole is considered true regardless of whether the match takes place or not.To recap: if told that the sample statement is false, we can deduce two things: It is raining is a true statement, and the match will be cancelled is a false statement. Also, we know a conditional statement with a false antecedent is always true.The converse of the statement is:If the match is cancelled (then) it is raining.Since we know (from the fact that the original statement is false) that the match is cancelled is false, the converse statement has a false antecedent and, by convention, such statements are always true.Thus the converse of a false conditional statement is always true. (A single example serves to show it's true in all cases since the logic is identical no matter what specific statements you apply it to.)If you are familiar with truth tables, the explanation is much easier. Here is the truth table for A = X->Y (i.e. A is the statement if X then Y) and B = Y->X (i.e. B is the converse statement if Y then X).X Y A BF F T TF F T TT F F TF T T FLooking at the last two rows of the A and B columns, when either of the statements is false, its converse is true.
false
independent variable
True
False. No matter what happens to the mineral, the streak will always remain the same.
false
Yes. Random true is always sometimes speaking untruthfully and yet speaks that random true is always true in which random true is a randomly true thing.
True AND False OR True evaluates to True. IT seems like it does not matter which is evaluated first as: (True AND False) OR True = False OR True = True True AND (False OR True) = True AND True = True But, it does matter as with False AND False OR True: (False AND False) OR True = False OR True = True False AND (False OR True) = False AND True = False and True OR False AND False: (True OR False) AND False = True AND False = False True OR (False AND False) = True OR False = True Evaluated left to right gives a different answer if the operators are reversed (as can be seen above), so AND and OR need an order of evaluation. AND can be replaced by multiply, OR by add, and BODMAS says multiply is evaluated before add; thus AND should be evaluated before OR - the C programming language follows this convention. This makes the original question: True AND False OR True = (True AND False) OR True = False OR True = True
I believe that this is a matter of opinion but my answer would be yes. Branden
Tautologies are always true.
false: matter cannot be destroyed
True. Matter and anti-matter
True