gnome.pango

// ⭐ THE MODULE, WHICH IS WHAT THE NAMESPACE PROMISES.
//
// In this index the namespace is the contract: `compat.xxx` is consumed with
// `#include`, an owner namespace like `gnome.xxx` exposes `import`. The test
// next to this file takes the header route; this one takes the module, so both
// doors are tested rather than assumed.
//
// ⚠️ THE TWO DOORS DO NOT COMPOSE. A TU that imports the module AND textually
// includes a pango or glib header reaches <time.h> twice — once through the
// module's global fragment, once directly — and the same `struct tm` becomes
// two entities. So a consumer picks ONE, and which one is decided by macros:
// a module cannot carry them. Code using `PANGO_TYPE_*` or `G_OBJECT` takes
// the header route; code using the function API imports and includes nothing.
#ifdef __linux__

import gnome.pango;   // re-exports gnome.gio, and glib/gobject behind it

// ⚠️ NO <cstdio> AND NO <cstring>. The module's global fragment already saw
// <stdio.h> and <string.h> through pango.h, and reaching them TEXTUALLY as
// well makes the same `struct _IO_FILE` two entities:
//
//     error: conflicting declaration 'struct _IO_FILE'
// …