Date: Wed, 20 Apr 2022 16:11:10 +0000
[Ben]
> Well, if we're getting technical, ISO C++ doesn't have compilers either
> (at least "compile" is nowhere in `[intro.defs]`). There *are*
> implementations. How they exist or work is not something I've seen in
> the C++ standard.
Yep; exactly right!
I believe there is a kernel of something useful that can be done here; but we need to be careful about the technical arguments being made.
-- Gaby
-----Original Message-----
From: Ext <ext-bounces_at_[hidden]> On Behalf Of Ben Boeckel via Ext
Sent: Wednesday, April 20, 2022 8:01 AM
To: René Ferdinand Rivera Morell via Ext <ext_at_[hidden]>
Cc: Ben Boeckel <ben.boeckel_at_[hidden]>; ISO C++ Tooling Study Group <sg15_at_[hidden]>; Peter Dimov <pdimov_at_[hidden]>; Daniel Ruoso <daniel_at_[hidden]>; Tom Honermann <tom_at_[hidden]>; Nathan Sidwell <nathan_at_[hidden]>
Subject: Re: [isocpp-ext] [SG15] Can we expect that all C++ source files can have the same suffix?
On Wed, Apr 20, 2022 at 08:49:18 -0500, René Ferdinand Rivera Morell via Ext wrote:
> On Wed, Apr 20, 2022 at 8:22 AM Daniel Ruoso via SG15 <sg15_at_[hidden]>
> wrote:
> > Why do we need to coerce compilers into playing this role?
>
> Because build systems are not part of the ISO standards from WG21. While we
> can't describe a build ecosystem in an ISO standard, C++ will need to be
> usable without the existence of anything except the "compiler".
Well, if we're getting technical, ISO C++ doesn't have compilers either
(at least "compile" is nowhere in `[intro.defs]`). There *are*
implementations. How they exist or work is not something I've seen in
the C++ standard.
And even given what I think you're referring to as a "compiler", I have
no idea what to do with such a thing without a standard library, linker,
or backing platform implementation (because no C++ stdlib I'm aware of
implements `std::filesystem` without an underlying platform).
--Ben
_______________________________________________
Ext mailing list
Ext_at_[hidden]
Subscription: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fext&data=05%7C01%7Cgdr%40microsoft.com%7C81eb28d75d3c46ba945c08da22de8f29%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637860636534277312%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PFOA%2BVCwdYDk4gdP3FWn9jpsBH9jDwiUHRrEsms0YDw%3D&reserved=0
Link to this post: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fext%2F2022%2F04%2F19080.php&data=05%7C01%7Cgdr%40microsoft.com%7C81eb28d75d3c46ba945c08da22de8f29%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637860636534277312%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2Bf6fzNFNMXAlZWsTM8Qy9m1Ca4saLRhPz0%2B1I5td2nc%3D&reserved=0
> Well, if we're getting technical, ISO C++ doesn't have compilers either
> (at least "compile" is nowhere in `[intro.defs]`). There *are*
> implementations. How they exist or work is not something I've seen in
> the C++ standard.
Yep; exactly right!
I believe there is a kernel of something useful that can be done here; but we need to be careful about the technical arguments being made.
-- Gaby
-----Original Message-----
From: Ext <ext-bounces_at_[hidden]> On Behalf Of Ben Boeckel via Ext
Sent: Wednesday, April 20, 2022 8:01 AM
To: René Ferdinand Rivera Morell via Ext <ext_at_[hidden]>
Cc: Ben Boeckel <ben.boeckel_at_[hidden]>; ISO C++ Tooling Study Group <sg15_at_[hidden]>; Peter Dimov <pdimov_at_[hidden]>; Daniel Ruoso <daniel_at_[hidden]>; Tom Honermann <tom_at_[hidden]>; Nathan Sidwell <nathan_at_[hidden]>
Subject: Re: [isocpp-ext] [SG15] Can we expect that all C++ source files can have the same suffix?
On Wed, Apr 20, 2022 at 08:49:18 -0500, René Ferdinand Rivera Morell via Ext wrote:
> On Wed, Apr 20, 2022 at 8:22 AM Daniel Ruoso via SG15 <sg15_at_[hidden]>
> wrote:
> > Why do we need to coerce compilers into playing this role?
>
> Because build systems are not part of the ISO standards from WG21. While we
> can't describe a build ecosystem in an ISO standard, C++ will need to be
> usable without the existence of anything except the "compiler".
Well, if we're getting technical, ISO C++ doesn't have compilers either
(at least "compile" is nowhere in `[intro.defs]`). There *are*
implementations. How they exist or work is not something I've seen in
the C++ standard.
And even given what I think you're referring to as a "compiler", I have
no idea what to do with such a thing without a standard library, linker,
or backing platform implementation (because no C++ stdlib I'm aware of
implements `std::filesystem` without an underlying platform).
--Ben
_______________________________________________
Ext mailing list
Ext_at_[hidden]
Subscription: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fext&data=05%7C01%7Cgdr%40microsoft.com%7C81eb28d75d3c46ba945c08da22de8f29%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637860636534277312%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PFOA%2BVCwdYDk4gdP3FWn9jpsBH9jDwiUHRrEsms0YDw%3D&reserved=0
Link to this post: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fext%2F2022%2F04%2F19080.php&data=05%7C01%7Cgdr%40microsoft.com%7C81eb28d75d3c46ba945c08da22de8f29%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637860636534277312%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2Bf6fzNFNMXAlZWsTM8Qy9m1Ca4saLRhPz0%2B1I5td2nc%3D&reserved=0
Received on 2022-04-20 16:11:12