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
Support 64-bit integer and/or unsigned 32-bit integer configuration types #11
Comments
Maybe we could model this on top of
|
That sounds good to me. What about |
Sure, the list could go on, and on, and on ... 😃 |
Postponing for a future release. |
Any update on this ? I need to store a 32-bit unsigned int and my only option at the moment is store it as a string, add a validation function to check that only valid uint32 can be set and do the conversion were appropriate. |
No update. Like most Open Source projects, libConfuse is driven by contributions from its users. Pull requests are welcome. |
Can I work on this? |
@bharsaklemukesh975 Sure, just outline first your ideas for the new API here. There are quite a few things to consider. Maybe have a look at, e.g., https://hyperrealm.github.io/libconfig/libconfig_manual.html for inspiration? |
so we have defines and types with CFG_INT, now we should add to support other integer type like CFG_UINT32, right? |
Essentially, yes. I'd just like first time contributors to elaborate a bit on their approach before they get a'crackin' |
It seems that on 32-bit *nix OS, the
CFG_INT
config type is signed 32-bit. I've got a config type that needs to be 64-bit. I've got another config type that needs to be unsigned 32-bit. I had been usingCFG_INT
fine on my 64-bit OS (CFG_INT
type is evidently signed 64-bit in that case), but it didn't work when I tried to cross-compile for a 32-bit ARM embedded Linux platform.For the unsigned 32-bit case, I guess I can do a custom validator and some typecasting to make it handle unsigned 32-bit. It would be nice for libconfuse to provide for unsigned 32-bit.
For the 64-bit values, it would be great if libconfuse would add support for 64-bit integer config types.
The text was updated successfully, but these errors were encountered: