Re: Why Python When There Is Perl?

On 3/24/2024 7:54 AM, Farley Flud wrote:

On Sun, 24 Mar 2024 12:21:17 +0000, Farley Flud wrote:
 

But (A IMP B) doesn't commute.
>

>
It does, in a sense.  The "opposite" of A => B is ~B => ~A.
>

 

But this means they don't commute. You'd have to change B to ~B and change A to ~A to establish the same statement. "The opposite of" is not the same as switching the sides.

To generate even more confusion, check out the following article.
Pay close attention to the "long" version:
 https://planetmath.org/logicalimplication
 

Yes, it mentions the difference between concurrence (he uses "then" for it) and implication ("implies"), but says, ".. Many writers draw a technical distinction between the [two]..." rather than stating anywhere what form of it is being used in a high level programming language.
To be honest, for a high level programmer that I think I am, none of that is relevant. It looks like the developers just wanted to create a way to single out a case when a condition is met, and another condition isn't met in the presence of the first condition (concurrent to it), then get a False result, and "AND" was too general for such cases. Cause AND doesn't distinguish between the logical antecedent and the logical consequence. I have no idea why they thought it was necessary to create such a tool in a high level language.
And from what I read by rBowman, it looks like its use to compare and check equality of two values at the bit level is funky at best. It would sometimes work and sometimes wouldn't work if you used IMP to check it.
--
This email has been checked for viruses by Avast antivirus software.
www.avast.com