-
Notifications
You must be signed in to change notification settings - Fork 3
feat: server-side C bindings #210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: server-side C bindings #210
Conversation
|
This pull request has been linked to Shortcut Story #210041: SDK Client C bindings. |
b6750d8 to
b5a3725
Compare
| LD_EXPORT(char*) | ||
| LDAllFlagsState_SerializeJSON(LDAllFlagsState state); | ||
|
|
||
| /** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This whole comment points to the danger of this kind of API.
Theoretically we could create a new typedef LDValueReference for these situations. And all the bindings. But it wouldn't have a binding for _Free. That'd prevent at least one error.
Another thing we could do is name this _ValueReference or something, rather than _Value.
| /** | ||
| * Enumeration of possible data source states. | ||
| */ | ||
| enum LDServerDataSourceStatus_State { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I admit these enums are quite ugly - but needed to rename so they don't clash with the client and can be independently changed.
Welcome to suggestions..
a4638a2 to
409dbda
Compare
Adds a hello app for the server-side C bindings. Also adds an app that includes both SDKs, to ensure they can coexist without symbol clashes.
This implements a set of C bindings for the server-side SDK.
Missing are flag notifier bindings, but this isn't implemented in the C++ side yet either.