The Bridge Hex
Decouple an abstraction from its implementation so both can vary independently.
✧ GANG OF FOUR LINEAGE & ARCANUM ✧
GOF DESIGN PATTERN: Bridge
ARCANUM SCHOOL: Transmutation // Dimensional Splitting
SCRIBE / ARCHON: Joshua Edward McLaughlin Cox
CANONICAL REGISTRATION:
// CODEX INCANTATION //
use fmt;
type Renderer = struct {
render_shape: *fn(name: str) void,
};
fn render_holo(name: str) void = {
fmt::printfln("Holographic projection of {}", name)!;
};
fn render_shadow(name: str) void = {
fmt::printfln("Shadow weaving of {}", name)!;
};
type Shape = struct {
name: str,
renderer: Renderer,
};
fn draw_shape(s: *Shape) void = {
s.renderer.render_shape(s.name);
};
export fn main() void = {
let holo = Renderer { render_shape = &render_holo };
let shadow = Renderer { render_shape = &render_shadow };
let cube = Shape { name = "Cube", renderer = holo };
draw_shape(&cube);
cube.renderer = shadow;
draw_shape(&cube);
};
The Bridge severs the hard link between an entity’s form and its materialization. In the cyber-arcane realms, a spell’s logic exists apart from whether it manifests as a hardlight hologram or a shadow-weave.
Runic Tags:
#structural
#bridge
#simple-systems-hexes