<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
        {mso-style-name:msonormal;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:"Calibri",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri",sans-serif;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">IPR isn’t for distribution.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> tooling-bounces@open-std.org <tooling-bounces@open-std.org>
<b>On Behalf Of </b>Corentin<br>
<b>Sent:</b> Saturday, February 9, 2019 2:21 PM<br>
<b>To:</b> WG21 Tooling Study Group SG15 <tooling@open-std.org><br>
<b>Cc:</b> michael_spencer@apple.com<br>
<b>Subject:</b> Re: [Tooling] Modules feedback<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I love the idea of IPR and I hope it will take off some day.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">However, the primary use case would be consumption by tools in the same environment as the representation was generated in.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A long as there are conditional preprocessor directives in sources, the only way to portably represent them will remain the full unprocessed textual content of said sources<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">If portable modules are something considered valuable, then conditional directives ( token soup ), will have to be replaced by conditionally-compiled well-formed C++ AST nodes ( static_if is one solution to that problem )<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Sat, 9 Feb 2019 at 23:05 Ville Voutilainen <<a href="mailto:ville.voutilainen@gmail.com">ville.voutilainen@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">On Sat, 9 Feb 2019 at 23:58, Ben Boeckel <<a href="mailto:ben.boeckel@kitware.com" target="_blank">ben.boeckel@kitware.com</a>> wrote:<br>
> I think we're eventually going to see projects wanting to not have<br>
> headers at all and that means that `-devel` packages will need<br>
> *something*. But I'm personally leaning towards it being a compiler<br>
> thing, not a language thing. IIRC, there was mention on Reddit of a<br>
> format Microsoft was working on for distilling a module down to an<br>
> interface description. Getting *that* as a shippable and consumable<br>
> format would be great.<br>
<br>
You mean <a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.stroustrup.com%2Fmacis09.pdf&data=02%7C01%7Cgdr%40microsoft.com%7C1bb9f30946944b1055c008d68edcee5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636853476882708402&sdata=oK5YZwr0zlsTciA2vGTjfQaWXY5mqiQGcuc7he0ekts%3D&reserved=0" target="_blank">
http://www.stroustrup.com/macis09.pdf</a>?<br>
Also <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGabrielDosReis%2Fipr&data=02%7C01%7Cgdr%40microsoft.com%7C1bb9f30946944b1055c008d68edcee5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636853476882718389&sdata=bSScaf9Dtezqj2tz%2FYnvYsBbgqizr8PosbTH9ezdLV0%3D&reserved=0" target="_blank">
https://github.com/GabrielDosReis/ipr</a><br>
_______________________________________________<br>
Tooling mailing list<br>
<a href="mailto:Tooling@isocpp.open-std.org" target="_blank">Tooling@isocpp.open-std.org</a><br>
<a href="https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.open-std.org%2Fmailman%2Flistinfo%2Ftooling&data=02%7C01%7Cgdr%40microsoft.com%7C1bb9f30946944b1055c008d68edcee5b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636853476882718389&sdata=bwhePz8DrOkwlsMpfPGuJ%2BpWO%2Btz27YeGhg7ApH7KEs%3D&reserved=0" target="_blank">http://www.open-std.org/mailman/listinfo/tooling</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</body>
</html>