VOID Native Interop
VOID can stay high level for normal game code while exposing an explicit unsafe path for C libraries, native structures, callbacks, stack memory, and low-level memory operations.
Native foundation
The native layer is project-controlled and explicit. The compiler emits ordinary C declarations/calls and lets the platform compiler/linker finish the job.
Current Pointer types, address-of, dereference, arithmetic, comparisons, parameters/returns, void*, pointer properties on unsafe classes/interfaces/value types, virtual/interface pointer-property dispatch, pointer constructors, and pointer ref/out/in constructor parameters inside the existing unsafe boundaries.
Current Unmanaged C-compatible structures cross the ABI with native field layout.
Current Native ref, out, and in lower to the pointer forms required by C APIs.
Current Type-qualified native bindings and [Native("symbol")] aliases keep VOID-facing names readable.
Current Projects declare native libraries/search paths; unsafe delegates can carry pointer returns/parameters and ref/out/in pointer forms; compatible static methods cross the ABI as callback function pointers; and callback parameters reuse the same ABI-safe by-reference lowering.
Current sizeof, memory copy/clear, and stackalloc cover focused unmanaged-memory needs.
Current Relative library paths keep native dependencies beside the project, while VOID library projects can emit their own lib<ProjectName>.a archives and stable [Export] C symbols for VOID or plain-C consumers.
Current Debug builds preserve VOID filenames and statement line numbers through generated C #line directives and standard GCC/Clang debug information.
Current VOID exception propagation is integrated with native and reusable-library boundaries without permitting uncontrolled raw unwinding through C ABI frames; invalid boundary cases receive focused diagnostics.
Why this matters
Audio, windowing, compression, platform APIs, custom C libraries, and future engine-facing native code can be bound without giving up the high-level language. VOID code can also be packaged back out as a reusable native archive, so the same ABI works in both directions. Native debugging still reports the originating VOID source lines.