mirror of
https://github.com/logos-messaging/nim-ffi.git
synced 2026-06-25 02:39:47 +00:00
8f15afce5c
`{.ffiEvent.}` previously accepted exactly one parameter, forcing every
multi-field event to declare a hand-written {.ffi.} payload type. The macro
now bundles two or more parameters into a synthesised, registered envelope
object named `<WireNamePascalCase>Payload`, whose fields are the parameters,
and dispatches an instance of it. A single parameter still rides the wire
directly (scalar or existing {.ffi.} object), so this is backwards
compatible. Because the envelope is registered like any {.ffi.} type, the
foreign bindings gain it as a first-class struct plus a typed handler.
The timer example gains an `on_job_scheduled(jobId, willRunCount)` event to
exercise the path; the C++ and Rust bindings are regenerated accordingly.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
C++ Bindings for nim-timer
Purpose
This folder contains auto-generated C++ bindings for the my_timer Nim library. It is generated from ../timer.nim and provides:
my_timer.hpp: High-level C++ class (MyTimerCtx) wrapping the FFI interfacemain.cpp: Example executable demonstrating how to use the bindingsCMakeLists.txt: Build configuration that compiles the Nim library and links the C++ example
How It's Generated
Generate or regenerate these bindings by running from the parent directory:
cd examples/timer
nimble genbindings_cpp
This command:
- Invokes the Nim compiler with
-d:targetLang:cppflag - Triggers
genBindings("examples/timer/cpp_bindings", "../timer.nim")intimer.nim - Creates/updates the generated binding files
Building the Example
cd examples/timer/cpp_bindings
cmake -S . -B build
cmake --build build
./build/example
Do Not Edit
The generated files in this folder are overwritten each time nimble genbindings_cpp runs. Any manual changes will be lost.