Title
What should <complex.h> do?
Status
c++17
Section
[support.c.headers]
Submitter
Richard Smith

Created on 2015-09-10.00:00:00 last changed 90 months ago

Messages

Date: 2016-09-12.04:46:33

Proposed resolution:

This wording is relative to N4527.

  1. Add a new paragraph before [depr.c.headers]/2:

    -?- The header <complex.h> behaves as if it simply includes the header <ccomplex>.

  2. Change in [depr.c.headers]/2:

    -2- Every other C header, each of which has a name of the form name.h, behaves as if each name placed in the standard library namespace by the corresponding cname header is placed within the global namespace scope. It is unspecified whether these names are first declared or defined within namespace scope (3.3.6) of the namespace std and are then injected into the global namespace scope by explicit using-declarations (7.3.3).

Date: 2016-09-09.00:00:00

[ 2016-09-09 Issues Resolution Telecon ]

Move to Tentatively Ready

Date: 2015-09-10.00:00:00

LWG issue 1134 removed the resolution of LWG 551, leaving an incorrect specification for the behavior of <complex.h>. This header is currently required to make std::complex (and associated functions) visible in the global namespace, but should not be so required.

History
Date User Action Args
2017-07-30 20:15:43adminsetstatus: wp -> c++17
2016-11-14 03:59:28adminsetstatus: pending -> wp
2016-11-14 03:55:22adminsetstatus: ready -> pending
2016-09-12 04:46:33adminsetmessages: + msg8514
2016-09-12 04:46:33adminsetstatus: new -> ready
2015-09-10 20:11:31adminsetmessages: + msg7517
2015-09-10 00:00:00admincreate