* Kevin Kofler via devel:
> Stephan Bergmann wrote:
>> Note that wrapping the header include in an extern declaration violates
>> C++ standard requirements. ("A translation unit shall include a header
>> only outside of any declaration or definition", [using.headers]/3)
>
> Yet, it is absolutely necessary for many C library headers that do not
> support C++ out of the box.
>
> I assume it was even the case for that particular GLib header at some point,
> or we would not have so many projects #including it in an extern "C" block.
Or system headers included by glib headers. I assume that glib has been
doing that properly for a long time, but it doesn't wrap system header
includes in this way.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
