Date: Fri, 3 Jun 2022 20:42:55 +0000
By that do you mean:
1. standard macros?
2. non-standard macro that change the implementation behavior?
-- Gaby
-----Original Message-----
From: Daniel Ruoso <daniel_at_ruoso.com>
Sent: Friday, June 3, 2022 1:30 PM
To: Gabriel Dos Reis <gdr_at_[hidden]>
Cc: sg15_at_lists.isocpp.org
Subject: Re: [SG15] "logical name" of importable headers
Em sex., 3 de jun. de 2022 às 15:52, Gabriel Dos Reis
<gdr_at_[hidden]> escreveu:
> Since the standards allow any C++ header (other that those inherited from C)
> to include any other C++ header, it follows that any C++ header can - in fact -
> include the entire standard library. Consequently, I suspect an implementation
> is permitted to replace #include of such standard headers with 'import std;'
> in C++23 and up
I can easily see consolidating a number of related headers into a
single header unit import, but I don't think we can transparently
switch to named modules without a significant behavior change, because
of macros.
daniel
1. standard macros?
2. non-standard macro that change the implementation behavior?
-- Gaby
-----Original Message-----
From: Daniel Ruoso <daniel_at_ruoso.com>
Sent: Friday, June 3, 2022 1:30 PM
To: Gabriel Dos Reis <gdr_at_[hidden]>
Cc: sg15_at_lists.isocpp.org
Subject: Re: [SG15] "logical name" of importable headers
Em sex., 3 de jun. de 2022 às 15:52, Gabriel Dos Reis
<gdr_at_[hidden]> escreveu:
> Since the standards allow any C++ header (other that those inherited from C)
> to include any other C++ header, it follows that any C++ header can - in fact -
> include the entire standard library. Consequently, I suspect an implementation
> is permitted to replace #include of such standard headers with 'import std;'
> in C++23 and up
I can easily see consolidating a number of related headers into a
single header unit import, but I don't think we can transparently
switch to named modules without a significant behavior change, because
of macros.
daniel
Received on 2022-06-03 20:43:02