Boolean algebra laws

A beginner guide to programming with .NET 5 and C#

Posted by Carl-Hugo Marcotte on August 29, 2021
Boolean algebra laws
Photo by Jefferson Santos on Unsplash

This article explores multiple Boolean algebra laws in a programmer-oriented way, leaving the mathematic notation aside. Those laws can be beneficial when working with boolean logic to simplify complex conditions. This article is very light in explanation and exposes the laws using C#. Don’t worry, I’m not recycling myself as a math teacher.

This article is part of a learn programming series where you need no prior knowledge of programming. If you want to learn how to program and want to learn it using .NET/C#, this is the right place. I suggest reading the whole series in order, starting with Creating your first .NET/C# program, but that’s not mandatory.

This article is part of a sub-series, starting with Introduction to Boolean algebra and logical operators. It is not mandatory to read all articles in order, but I strongly recommend it, especially if you are a beginner. If you are already reading the whole series in order, please discard this word of advice.

Let’s explore Boolean algebra laws in alphabetical order. Some are very simple, while some may seem more complex, but all are very useful tools.

In the examples, the variables (A, B, C) are all booleans, like this:

bool A, B, C;

Absorption Law

The absorption law goes as follow:

  • A && (A || B) always equals A
  • A || A && B always equals A

Annulment Law

The annulment law goes as follow:

  • A && false is always false
  • A || true is always true

Associative Law

The associative law says that no matter the order or priority of the OR comparisons, the result will always be the same. The following conditions yield the same result:

  • A || (B || C)
  • (A || B) || C
  • (A || C) || B
  • A || B || C

Complement Law

The complement law goes as follow:

  • A && !A is always false
  • A || !A is always true

Commutative Law

The commutative law goes as follow:

  • A && B is the same as B && A
  • A || B is the same as B || A

Consensus Law

The consensus law goes as follow:

  1. (A || B) && (!A || C) && (B || C) is equivalent to (A || B) && (!A || C)
  2. A && B || A && C || B && C is equivalent to A && B || A && C

These two might be harder to grasp, so here’s my take at a quick explanation:

  1. In the first two comparisons of (A || B) && (!A || C) && (B || C), A and !A are almost cancelling themselves, leaving the outcome of the comparison to B and C. Based on that fact, no matter the values, the last comparison && (B || C) becomes useless (already evaluated).
  2. The second one is similar. In the first two comparisons of A && B || A && C || B && C, we test B and C, making the last comparison void || B && C.

Word of advice: it is not mandatory to remember the consensus law, so feel free to skip this one if you think it’s too complicated for today. You can always come back to it later.

De Morgan’s laws

This one is very interesting and can be handy from time to time. In plain English, De Morgan’s laws are:

  • The negation of a disjunction is the conjunction of the negations.
  • The negation of a conjunction is the disjunction of the negations.

Logical conjunction means AND (&&), and the logical disjunction means OR (||). Unless you are into mathematics, you don’t have to remember that.

Now to the part that interests us, in C#, De Morgan’s laws are:

  • !(A || B) is equivalent to !A && !B
  • !(A && B) is equivalent to !A || !B

Distributive Law

The distributive law goes as follow:

  • A && B || A && C is equivalent to A && (B || C)
  • (A || B) && (A || C) is equivalent to A || B && C

Double negation law

The double negation law says that two negations negate themselves. In C# this looks like:

  • !!A is equivalent to A

Identity Law

The identity law goes as follow:

  • A && true always equals A
  • A || false always equals A

Idempotent Law

The idempotent law goes as follow:

  • A && A always equals A
  • A || A always equals A

Redundancy Law

The redundancy law goes as follow:

  • (A || B) && (A || !B) always equals A
  • A && B || A && !B always equals A
  • (A || !B) && B is equivalent to A && B
  • A && !B || B is equivalent to A || B

Conclusion

In this article, we explored a bunch of Boolean algebra laws from a C# programmer perspective. You can find information on them, including mathematic proofs, online or in books if you are into maths. Personally, I prefer the plain C# version, so that’s why I translated them to this here. Even if some of those laws might seem a bit too complicated to remember, don’t be discouraged; even the simplest ones are helpful: start there.

Programming is like playing LEGO® blocks: we can combine all of those laws, which are logic patterns. For example, !(!A || !B) looks complicated, but after applying De Morgan’s law, it becomes equivalent to !(!(A && B)). By removing the useless parenthesis we end up having !!(A && B), which exposes a double negation. Applying the double negation law leads to A && B. That simplified version of the original condition looks way simpler, doesn’t it?

Learning the basics is helpful in the long run. If you have a good memory, feel free to memorize all of this as a starting point. If you don’t, don’t worry, learn them one by one. The idea is to simplify your code, so it reaches a more maintainable state. With a bit of time, you will most likely know and apply many (if not all) of them without thinking about it. Just start with the simplest ones, bookmark the article, and learn the others later. Understanding rules, laws, and concepts should get you further than just remembering them; but that takes more time.

Fun fact: I’ve run many interviews in 2021, and one of my favorite technical questions is based on complicated conditions that can be simplified using some of those laws. And no, I’m not looking for candidates that know the name of the laws, just if they can resolve a complex if-statement and how.

Please leave your questions or comments below or drop me a Tweet.

Next step

It is now time to move to the next article: Introduction to numbers and arithmetic operators that’s coming soon. Stay tuned by following me:

Table of content

Now that you are done with this article, please look at the series’ content.

Articles in this series
Creating your first .NET/C# program
In this article, we are creating a small console application using the .NET CLI to get started with .NET 5+ and C#.
Introduction to C# variables
In this article, we explore variables. What they are, how to create them, and how to use them. Variables are essential elements of a program, making it dynamic.
Introduction to C# constants
In this article, we explore constants. A constant is a special kind of variable.
Introduction to C# comments
In this article, we explore single-line and multiline comments.
How to read user inputs from a console
In this article, we explore how to retrieve simple user inputs from the console. This will help us make our programs more dynamic by interacting with the user.
Introduction to string concatenation
In this article, we dig deeper into strings and explore string concatenation.
Introduction to string interpolation
In this article, we explore string interpolation as another way to compose a string.
Escaping characters in C# strings
In this article, we explore how to escape characters like quotes and how to write special character like tabs and new lines.
Introduction to Boolean algebra and logical operators
This article introduces the mathematical branch of algebra that evaluates the value of a condition to true or false.
Using if-else selection statements to write conditional code blocks
In this article, we explore how to write conditional code using Boolean algebra.
Using the switch selection statement to simplify conditional statements blocks
In this article, we explore how to simplify certain conditional blocks by introducing the switch statement.
Boolean algebra laws You are here
This article explores multiple Boolean algebra laws in a programmer-oriented way, leaving the mathematic notation aside.
More to come Most likely in Q1 of 2022





Comments