Gain insights into software design patterns in C, explore their implementation, discover underlying principles, and learn to build a vocabulary for better communication and coding practices.

c.tar.gz

main+customer.c

main+customer.c-copy

watches

customers

observer

Reactor

Reactor-copy

observer-copy

Software design patterns are a valuable tool in any software developer's skill set. However, most design patterns are described in the context of an object-oriented programming language such as C++ or Java. The C language is sadly absent in the pattern literature. This course is here to change that by demonstrating that it is possible to use patterns in C programs and how it adds benefits to C programmers. You will learn why design patterns are more of a communication tool than technical solutions, and how patterns let you build and share a common vocabulary that simplifies communication.

The course presents a number of patterns and explains how to implement them in C. Each pattern is introduced via the problem it solves and the domains where the pattern can be used. We also discuss the underlying design principles as well as the trade-offs when applying the pattern. Finally, the course covers a set of coding idioms that will guide you when applying design patterns in C.

Software Design Patterns in C

Our journey through the patterns will start with a language level pattern that decouples interface from
implementation, thus: 
* **Improving encapsulation.** 
* **Providing loose dependencies.**

This pattern will lay the foundation for many of the subsequent patterns in this course.

Imagine that you are close to a project deadline when your project manager rushes into your office citing that the test team found a problem with your code. According to the team, the code cannot register more than 42 orders for a given customer.

In this lesson, we will learn why we need the FIRST-CLASS ADT pattern.

Introduction to Pattern in C

The First-Class ADT Pattern

The State Pattern

The Strategy Pattern

The Observer Pattern

The Reactor Pattern

Idiomatic Expressions

Conclusion

Why We Need First-Class ADT Pattern

First-Class ADT pattern