logger

Purpose

The logger port defines the common logging abstraction used by the foundation layer.

It provides:

• a borrower-facing runtime API for emitting log messages,
• lifecycle services for destroying logger_t handles,
• Composition Root services for preparing injected runtime dependencies,
• adapter-facing contracts used to bind concrete logging backends to the generic logger port.

The module is designed to separate:

• the generic logging contract,
• the concrete adapter implementations,
• the Composition Root wiring used to connect both.

Public API

• logger API

Sub-APIs:

• borrowers API
• lifecycle API
• CR API
• adapters API

Architectural role

The logger module is a foundation port. It defines the public logging boundary used by runtime code, while concrete adapter modules provide backend-specific implementations.

Typical responsibilities:

• expose the public logger_t handle and status model,
• route borrower-facing logging operations through adapter-bound dispatch tables,
• manage logger handle destruction,
• provide the public environment contract used to inject runtime dependencies.

Main concepts

Borrower-facing usage

Runtime code emits messages through logger_t handles using the public borrower API:

• logger_log()

Adapter binding

Concrete adapters bind backend logic to the generic logger port through:

• logger_vtbl_t
• logger_create()

Runtime dependency injection

The Composition Root can prepare the runtime environment of the port through:

• logger_env_t
• logger_default_env()

Related modules

Concrete adapters for this port are documented in the surrounding logger family.

See:

• logger family

See also

• logger specifications
• logger family tests page
• logger tests group