Bridge Method Design Pattern

The Bridge Pattern is a structural design pattern that separates abstraction from implementation, allowing them to vary independently. This pattern is particularly useful in embedded systems where we may have different platforms, devices, or hardware that need to be supported.

Let’s see a simple example of the Bridge Pattern in C for embedded systems:

C




#include <stdio.h>
 
// Implementor interface
// This represents the implementation interface that concrete implementors will implement
typedef struct {
    void (*sendData)(const char *data);
} Implementor;
 
// Concrete Implementor A
typedef struct {
    Implementor implementor;
} ConcreteImplementorA;
 
void sendA(const char *data) {
    printf("Sending data using Implementor A: %s\n", data);
}
 
void initializeConcreteImplementorA(ConcreteImplementorA *this) {
    this->implementor.sendData = sendA;
}
 
// Concrete Implementor B
typedef struct {
    Implementor implementor;
} ConcreteImplementorB;
 
void sendB(const char *data) {
    printf("Sending data using Implementor B: %s\n", data);
}
 
void initializeConcreteImplementorB(ConcreteImplementorB *this) {
    this->implementor.sendData = sendB;
}
 
// Abstraction interface
// This represents the abstraction interface that concrete abstractions will implement
typedef struct {
    Implementor implementor;
    void (*send)(const char *data);
} Abstraction;
 
// Refined Abstraction
typedef struct {
    Abstraction abstraction;
} RefinedAbstraction;
 
void sendData(RefinedAbstraction *this, const char *data) {
    printf("Refined Abstraction is sending data: %s\n", data);
    this->abstraction.implementor.sendData(data);
}
 
void initializeRefinedAbstraction(RefinedAbstraction *this, Implementor *implementor) {
    this->abstraction.implementor = *implementor;
    this->abstraction.send = sendData;
}
 
int main() {
    ConcreteImplementorA concreteImplementorA;
    initializeConcreteImplementorA(&concreteImplementorA);
 
    ConcreteImplementorB concreteImplementorB;
    initializeConcreteImplementorB(&concreteImplementorB);
 
    RefinedAbstraction refinedAbstractionA;
    initializeRefinedAbstraction(&refinedAbstractionA, &concreteImplementorA.implementor);
    refinedAbstractionA.abstraction.send("Hello from Abstraction A");
 
    RefinedAbstraction refinedAbstractionB;
    initializeRefinedAbstraction(&refinedAbstractionB, &concreteImplementorB.implementor);
    refinedAbstractionB.abstraction.send("Hello from Abstraction B");
 
    return 0;
}


Explanation of the above Code:

  • Implementor is an interface that declares the operations that concrete implementors must implement.
  • ConcreteImplementorA and ConcreteImplementorB are concrete implementations of the Implementor interface.
  • Abstraction is an interface that declares the operations that concrete abstractions must implement.
  • RefinedAbstraction is a refined abstraction that extends the abstraction interface.
  • Main function demonstrates how you can use the Bridge Pattern to decouple abstractions from implementations and switch implementations dynamically.

Design Patterns for Embedded Systems in C

When working with embedded systems in C, there are so many design patterns that are particularly very useful. Many design patterns can be applied to embedded systems development in C. In this article, we will discuss design patterns for Embedded Systems in C, let’s see all of them one by one with the help of examples.

Important Topics for Design Patterns for Embedded Systems in C

  • What is a Design Pattern?
  • Creational Design Patterns for Embedded Systems in C
    • Factory Method Design Pattern
    • Object Method Design Pattern
    • Opaque Method Design Pattern
    • Singleton Method Design Pattern
  • Structural Design Patterns for Embedded Systems in C
    • Callback Method Design Patterns
    • Inheritance Method Design Pattern
    • Virtual API Method Design Pattern
  • Other Design Patterns for Embedded System in C
    • Bridge Method Design Pattern
    • Concurrency Method Design Pattern
    • Spinlock Method Design Pattern
    • Mutex Method Design Pattern
    • Conditional Method Design Pattern
    • Behavioral Method Design Pattern

Similar Reads

1. What is a Design Pattern?

Design patterns are defined as the general reusable solutions to the common problems that occur during software development and software designing....

2. Creational Design Pattern for Embedded Systems in C

In embedded systems development in C, creational design patterns are used to abstract the instantiation process of objects, providing flexibility in creating and configuring objects....

2.1 Factory Method Design Pattern

One commonly used creational design pattern is the Factory Method Pattern. Let’s see an example of how we can implement the Factory Method Pattern in C for an embedded system:...

2.2 Object Method Design Pattern

...

2.3 Opaque Method Design Pattern

In the embedded systems programming in C, the Object Pattern is typically implemented using structures and functions that operate on those structures. While C does not have native support for object-oriented programming....

2.4 Singleton Method Design Pattern

...

3. Structural Design Patterns for Embedded Systems in C

In the embedded systems programming, an opaque pattern is often used to hide the implementation details of a data structure or module from the outside world. This helps in encapsulating the internal details, providing a clean interface, and enhancing code maintainability....

3.1 Callback Method Design Patterns

...

3.2 Inheritance Method Design Pattern

...

3.3 Virtual API Method Design Pattern

The Singleton Pattern is basically a type of design pattern that restricts the instantiation of a class to a single instance and provides a global point of access to that instance. This pattern is often used to control access to resources such as databases, file systems, or network connections....

4. Other Design Patterns for Embedded System in C

...

4.1 Bridge Method Design Pattern

Structural design patterns in embedded systems help to organize and structure the code in a way that makes it more modular, flexible, and easier to maintain....

4.2 Concurrency Method Design Pattern

The callback pattern in embedded systems is a design pattern where a function (callback function) is registered to be called later when a specific event or condition occurs....

4.3 Spinlock Method Design Pattern

...

4.4 Mutex Method Design Pattern

In embedded systems programming with C, inheritance is not directly supported as it is in some object-oriented languages like C++....

4.5 Conditional Method Design Pattern

...

4.6 Behavioral Method Design Pattern

The Virtual API design pattern, sometimes called the Virtual Function Table (VFT) pattern, is a valuable technique in embedded C programming for providing a common interface to different implementations of the same functionality....

Conclusion

...

Contact Us