Namespaces (Scope Containers)

In C, to avoid naming conflicts, we rely on long prefixes (e.g., HAL_UART_Init, HAL_SPI_Init).

In C++, a Namespace is a declarative region that provides a scope to identifiers (names of types, functions, variables, etc.). It allows you to group related code together and reuse common names like Init, Start, or Status without collision.

Syntax & Usage

1. Basic Declaration

Wrap your declarations in a namespace block.

namespace UART {
    int baud_rate;
    void init() { /* ... */ }
}

namespace SPI {
    int baud_rate; // No conflict with UART::baud_rate
    void init() { /* ... */ } // No conflict with UART::init
}

2. Accessing Members

Use the Scope Resolution Operator (::).

UART::init();
SPI::init();
UART::baud_rate = 9600;

3. The using Directive

You can import a namespace into the current scope to avoid typing the prefix repeatedly.

Warning: Use with caution (see Pitfalls).

using namespace UART;
init(); // Calls UART::init() implicitly

Scope Visualization

Namespaces create logical "folders" for your code symbols.

Relevance in Embedded/Firmware

1. Clean Driver APIs

Embedded systems have many peripherals (I2C, SPI, UART, CAN) that perform identical actions: read, write, init, reset.

Namespaces allow you to use these intuitive names for every driver without C-style prefix hell.

• CAN::send(msg)
• WiFi::send(packet)
• Log::send(string)

2. Board Support Packages (BSP)

You can switch hardware configurations easily using namespace aliases.

// In config.h
namespace SensorBus = I2C1; // Alias

// In main.cpp
SensorBus::read(); // Reads from I2C1. Change alias to switch to SPI.

3. Avoiding Library Collisions

If you use two external libraries (e.g., a "Motor Library" and a "Display Library") and both define a struct named Point or Color, C compilation fails.

If they are wrapped in namespaces (MotorLib::Point, GuiLib::Point), they coexist peacefully.

Common Pitfalls (Practical Tips)

namespace HW = Board::Drivers::Hardware;
HW::init();