Expose the generated MEOS surface, one file per header - #17
Merged
estebanzimanyi merged 1 commit intoSep 2, 2026
Merged
Conversation
The generated surface is what a consumer of this binding calls, so it is public: `MEOS.NET.Functions.Meos` carries a static method for each of the 4825 functions the catalog declares, split across one file per MEOS header exactly as the catalog groups them — `Meos.meos.g.cs`, `Meos.meos_geo.g.cs`, `Meos.meos_cbuffer.g.cs`, through 29 headers — with the P/Invoke declarations behind them in `Meos.Native.g.cs`. This is the shape GoMEOS ships, whose `functions/` package is likewise the catalog projected one file per header and is the surface its README points a user at. A method is the C name in PascalCase: `tfloat_in` reads `TfloatIn`, `meos_initialize` reads `MeosInitialize`. That is the spelling GoMEOS exports, so the ecosystem carries one rule rather than a per-binding invention, and the generator refuses a catalog in which two C names share one C# name rather than emitting a surface that does not compile. Every MEOS function is therefore reachable without a hand-written wrapper, including the operator families the object model leaves unclassified.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The generated surface is what a consumer of this binding calls, so it is
public:
MEOS.NET.Functions.Meoscarries a static method for each of the4825 functions the catalog declares, split across one file per MEOS header
exactly as the catalog groups them —
Meos.meos.g.cs,Meos.meos_geo.g.cs,Meos.meos_cbuffer.g.cs, through 29 headers — with the P/Invoke declarationsbehind them in
Meos.Native.g.cs. This is the shape GoMEOS ships, whosefunctions/package is likewise the catalog projected one file per header andis the surface its README points a user at.
A method is the C name in PascalCase:
tfloat_inreadsTfloatIn,meos_initializereadsMeosInitialize. That is the spelling GoMEOS exports,so the ecosystem carries one rule rather than a per-binding invention, and the
generator refuses a catalog in which two C names share one C# name rather than
emitting a surface that does not compile.
Every MEOS function is therefore reachable without a hand-written wrapper,
including the operator families the object model leaves unclassified.