Date: Mon, 24 Jun 2024 17:01:43 +0000
The Modules TR list existing practice as accepted by implementations.
I believe build systems that support modules already take care of differences.
-- Gaby
From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Jonathan Wakely via SG15
Sent: Monday, June 24, 2024 10:31 AM
To: sg15_at_[hidden]
Cc: Jonathan Wakely <cxx_at_kayari.org>; James <james.business.84_at_[hidden]>
Subject: Re: [isocpp-sg15] State of the modules today
On Mon, 24 Jun 2024 at 15:31, James via SG15 <sg15_at_[hidden]<mailto:sg15_at_[hidden]>> wrote:
> One particular thing I’m puzzled by is the lack of a standard file extension accepted by the major compilers.
There is no standard file extension for header files either, or C++ source files. It would be _more_ puzzling if we'd gone against the grain and standardized a file extension! Especially as the C++ standard doesn't require an implementation to even support "file extensions", as the naming of source files on a file system is out of scope for the C++ standard.
I believe build systems that support modules already take care of differences.
-- Gaby
From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Jonathan Wakely via SG15
Sent: Monday, June 24, 2024 10:31 AM
To: sg15_at_[hidden]
Cc: Jonathan Wakely <cxx_at_kayari.org>; James <james.business.84_at_[hidden]>
Subject: Re: [isocpp-sg15] State of the modules today
On Mon, 24 Jun 2024 at 15:31, James via SG15 <sg15_at_[hidden]<mailto:sg15_at_[hidden]>> wrote:
> One particular thing I’m puzzled by is the lack of a standard file extension accepted by the major compilers.
There is no standard file extension for header files either, or C++ source files. It would be _more_ puzzling if we'd gone against the grain and standardized a file extension! Especially as the C++ standard doesn't require an implementation to even support "file extensions", as the naming of source files on a file system is out of scope for the C++ standard.
Received on 2024-06-24 17:01:47