Skip to content
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

Open Source and Commercial Users of WinReg #45

Open
GiovanniDicanio opened this issue Nov 30, 2021 · 6 comments
Open

Open Source and Commercial Users of WinReg #45

GiovanniDicanio opened this issue Nov 30, 2021 · 6 comments

Comments

@GiovanniDicanio
Copy link
Owner

GiovanniDicanio commented Nov 30, 2021

I'd like to compile a list of open source and commercial users of this C++ WinReg library.

If anyone would like to contribute and is willing to share this information, please add that below.

Thank you.

@wolfv
Copy link

wolfv commented Nov 30, 2021

Hi @GiovanniDicanio we're using it in the mamba project

@GiovanniDicanio
Copy link
Owner Author

Hi @wolfv! Thank you very much for your comment and for opening the user list :) Much appreciated!

@wolfv
Copy link

wolfv commented Nov 30, 2021

PS: I'll package it for the conda-forge channel in the coming days. If you want to be a co-maintainer of the package, let me know. (It's a very low-effort job, especially since the code here seems very stable!).

Repository owner deleted a comment from sszth Feb 25, 2022
@mattmcde78
Copy link

mattmcde78 commented Nov 9, 2024

@GiovanniDicanio we're using it in MDaemon Technologies (https://mdaemon.com/) commercial SecurityGateway for Email project. Great work!

We are using UTF8 for strings in the code base. Adding interfaces that accept UTF8 strings (and converting internally to/from Unicode) would make our usage a bit cleaner. Perhaps a WINREG_USE_UTF8 preprocessor definition?

@GiovanniDicanio
Copy link
Owner Author

@mattmcde78 Thank you very much for sharing!

Your UTF-8 suggestion is interesting. Thinking a bit about it, always translating between external UTF-8 strings at the WinReg interface boundary with internal UTF-16 used by Windows API calls could add some overhead, especially for those using UTF-16 in their C++ code bases.
On the other hand, switching that behavior on or off via a preprocessor macro definition seems interesting and could avoid the risk of overhead previously mentioned. I'll think more about it.

Thanks again for sharing your usage and for this suggestion!

@GiovanniDicanio
Copy link
Owner Author

@mattmcde78 : I created a new issue #75 to talk about that. It would be great if you could try some of the current code and give me some feedback in that issue page. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants