the c abi
the flat c exports, opaque handles, and the rules that never move
window.abi.dll is a thin shell over the real c++ api, not the other way round. flat c exports over
opaque handles, so anything that can call a c function can drive the lib
#include "abi/window_abi.h"plain c, no class and no exception ever crosses it, and it is the whole of what stock ahk sees
two rules that never move
| rule | what it means for you |
|---|---|
| the ordinals froze | a new export goes at the END of its list and the version bumps, nothing is ever inserted or reordered |
| the version is checked on load | a mismatch throws, because an old dll fills every enum value with something else |
a script has no compiler to tell it anything, it just gets numbers. that is why both rules exist and why neither is negotiable
the pages
| how the abi is designed | the WHY, the freeze rules, what is deliberately not exported |
| the call shape | start here, the one shape every export takes, the statuses, the handles |
| the window | making one, painting it, the three pumps, reading it back |
| controls | the generic half, the box, the tree, layout hints |
| containers | the overlay slot, the flow cursor, scrolling |
| theme | a theme and its tokens |
| tweens | the curves and the one shared ticker |
| events | the queue, and the three rules that bite |
a question about what a wrapped call means is answered by the c++ header underneath it,
host.h,control.h,layout.h,theme.h,tween.h, over in the c++ api