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

C++ 17 and C++ 20 build issues due to ambiguity of data type names #230

Open
alas2 opened this issue Sep 20, 2024 · 1 comment
Open

C++ 17 and C++ 20 build issues due to ambiguity of data type names #230

alas2 opened this issue Sep 20, 2024 · 1 comment
Labels
feature bug Something isn't working

Comments

@alas2
Copy link

alas2 commented Sep 20, 2024

Could we please have this library support C++ 17 and C++ 20 along with the existing support for C++14? Currently if I build with C++ 14 there are no issues but when switching to C++20, I get errors about ambiguous data type, see below. For example std::byte added since C++ 17 is causing an ambiguity. Also, auto_ptr are not supported since C++ 17, probably can be replaced by unique_ptr.

I think, if "using namespaces" are used only in C++ files after the last #include the issue would be fixed. In header files full qualifiers must be used.

1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.22000.0\shared\rpcndr.h(192,14): error C2872: 'byte': ambiguous symbol
1>C:\Program Files (x86)\Windows Kits\10\Include\10.0.22000.0\shared\rpcndr.h(191,23): message : could be 'unsigned char byte'
1>C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.34.31933\include\cstddef(28,12): message : or 'std::byte'

Thanks.

@alas2 alas2 added the feature bug Something isn't working label Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants
@alas2 and others