Date: Tue, 3 May 2022 19:30:32 +0000
> While at it, can we also agree to call BMI a BMI and not CMI or IFC?
MSVC uses BMI when it means BMI 😊
IFC is the MSVC's concrete container implementation, i.e. file format, of BMI that goes beyond what is meant and intended by BMI.
> It must be really baffling to someone looking from the outside that
> we have three different terms for this.
Indeed.
-- Gaby
-----Original Message-----
From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Boris Kolpackov via SG15
Sent: Tuesday, May 3, 2022 7:18 AM
To: Nathan Sidwell via SG15 <sg15_at_lists.isocpp.org>
Cc: Boris Kolpackov <boris_at_[hidden]m>; Tom Honermann <tom_at_honermann.net>; Nathan Sidwell <nathan_at_acm.org>
Subject: Re: [SG15] P2581R0: Specifying the Interoperability of Binary Module Interface Files
Nathan Sidwell via SG15 <sg15_at_lists.isocpp.org> writes:
> On 5/3/22 08:48, Gabriel Dos Reis via SG15 wrote:
> >I have a lot to say in this thread, but a request for the CMake folks:
> >
> >>CXX_MODULE_HEADERS
> >
> >Please, can we avoid "module headers" or "header modules" as terminology in the community?
> >We've settled on "header units". If we need something more than that, please let's work on it.
>
> Absolutely. Also, in some contexts 'modules' can refer to both 'named
> modules' and 'header units', and in others just the former. It is best to
> be unambiguous.
While at it, can we also agree to call BMI a BMI and not CMI or IFC?
It must be really baffling to someone looking from the outside that
we have three different terms for this.
_______________________________________________
SG15 mailing list
SG15_at_[hidden]cpp.org
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fsg15&data=05%7C01%7Cgdr%40microsoft.com%7C8612ab06805f4a4fe76808da2d0fcaa3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637871843102520480%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Oug0b6Fw2e%2FAVxMidGGiEaiDTgUiDEi%2FDpuh7EYZg0I%3D&reserved=0
MSVC uses BMI when it means BMI 😊
IFC is the MSVC's concrete container implementation, i.e. file format, of BMI that goes beyond what is meant and intended by BMI.
> It must be really baffling to someone looking from the outside that
> we have three different terms for this.
Indeed.
-- Gaby
-----Original Message-----
From: SG15 <sg15-bounces_at_[hidden]> On Behalf Of Boris Kolpackov via SG15
Sent: Tuesday, May 3, 2022 7:18 AM
To: Nathan Sidwell via SG15 <sg15_at_lists.isocpp.org>
Cc: Boris Kolpackov <boris_at_[hidden]m>; Tom Honermann <tom_at_honermann.net>; Nathan Sidwell <nathan_at_acm.org>
Subject: Re: [SG15] P2581R0: Specifying the Interoperability of Binary Module Interface Files
Nathan Sidwell via SG15 <sg15_at_lists.isocpp.org> writes:
> On 5/3/22 08:48, Gabriel Dos Reis via SG15 wrote:
> >I have a lot to say in this thread, but a request for the CMake folks:
> >
> >>CXX_MODULE_HEADERS
> >
> >Please, can we avoid "module headers" or "header modules" as terminology in the community?
> >We've settled on "header units". If we need something more than that, please let's work on it.
>
> Absolutely. Also, in some contexts 'modules' can refer to both 'named
> modules' and 'header units', and in others just the former. It is best to
> be unambiguous.
While at it, can we also agree to call BMI a BMI and not CMI or IFC?
It must be really baffling to someone looking from the outside that
we have three different terms for this.
_______________________________________________
SG15 mailing list
SG15_at_[hidden]cpp.org
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fsg15&data=05%7C01%7Cgdr%40microsoft.com%7C8612ab06805f4a4fe76808da2d0fcaa3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637871843102520480%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Oug0b6Fw2e%2FAVxMidGGiEaiDTgUiDEi%2FDpuh7EYZg0I%3D&reserved=0
Received on 2022-05-03 19:30:34