Skip to content

YaHTTP: Better detection of whether C++11 features are available #12589

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

Merged
merged 1 commit into from
Feb 27, 2023

Conversation

rgacogne
Copy link
Member

Short description

The previous version relied on having HAVE_CXX11 defined, which is not true when you are compiling with C++17, for example, even though the C++11 features are available (HAVE_CXX17 is defined but that does not help).

I'll open a pull request in the YaHTTP repo as well.

Checklist

I have:

  • read the CONTRIBUTING.md document
  • compiled this code
  • tested this code
  • included documentation (including possible behaviour changes)
  • documented the code
  • added or modified regression test(s)
  • added or modified unit test(s)

The previous version relied on having `HAVE_CXX11` defined, which
is not true when you are compiling with C++17, for example, even
though the C++11 features are available (`HAVE_CXX17` is defined
but that does not help).
@rgacogne
Copy link
Member Author

cmouse/yahttp#27

@omoerbeek
Copy link
Member

There's also cmouse/yahttp#26 , which provides a more fundamental approach.

@rgacogne
Copy link
Member Author

That would indeed be better, but I would prefer not diverging too much from upstream, so unless we feel 26 might be merged quickly I would prefer merging this one in the meantime, especially since it was already merged upstream.

@omoerbeek
Copy link
Member

Yes, agreed.

@rgacogne rgacogne merged commit 7ad93ed into PowerDNS:master Feb 27, 2023
@rgacogne rgacogne deleted the yahttp-cxx11-detection branch February 27, 2023 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants