<div dir="ltr"><div><br></div><div>Nice document.</div><br><div><span style="color:rgb(33,33,33)">6.4 I believe LHU imported through include will need to be identified by either</span></div><div><ul><li><font color="#212121" size="2">Having a manually maintained list of LHU</font></li><li><font color="#212121" size="2">Parsing all files in the projects/dependency and assuming that files that are not imported with import at least once are not LHU</font></li></ul><div><font color="#212121" size="2"><br></font></div></div><div><font color="#212121" size="2">I agree that letting the compiler decides to treat an include as an LHU without the blessing of the build system would be asking for trouble</font></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 8 Feb 2019 at 17:51 Gabriel Dos Reis via Ext <<a href="mailto:ext@lists.isocpp.org">ext@lists.isocpp.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Early feedback regarding section 6.3 and 6.4.<br>
<br>
Concern in 6.3:<br>
The description there is notional, not a requirement that needs to be followed by the letter by compilers.<br>
There is an alternative formulation that uses the notion or "semantics abstract graph" (term defined in the Modules TS) that does not rely on synthesized header unit.<br>
<br>
Concern in 6.4:<br>
The way to import of "header import" is that of using a precompiled header file. If CMAKE already supports uses of PCHs, then the machinery is already there.<br>
For every import of a header H, there would be a rule for building say H.pch unless there is already a H.pch supplied by the system or other sources.<br>
<br>
<br>
Early feedback on section 7.<br>
That ask in 7.1 looks immensely reasonable to me; we have been considering similar for a while. <br>
The Visual C++ team would be happy to team up with other tool vendor to provide an open source version.<br>
<br>
-- Gaby<br>
<br>
| -----Original Message-----<br>
| From: <a href="mailto:tooling-bounces@open-std.org" target="_blank">tooling-bounces@open-std.org</a> <<a href="mailto:tooling-bounces@open-std.org" target="_blank">tooling-bounces@open-std.org</a>> On<br>
| Behalf Of Ben Boeckel<br>
| Sent: Friday, February 8, 2019 7:55 AM<br>
| To: WG21 Tooling Study Group SG15 <<a href="mailto:tooling@open-std.org" target="_blank">tooling@open-std.org</a>><br>
| Subject: [Tooling] [D1483] How CMake supports Fortran modules and its<br>
| applicability to C++<br>
| <br>
| Hi,<br>
| <br>
| Here is copy of Kitware's paper to be discussed at Kona. I have a PDF,<br>
| but it was too large to attach to the list. I'll be at Kona, but the<br>
| other authors are not able to make it.<br>
| <br>
| An HTML version is hosted here:<br>
| <br>
| <br>
| <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmath" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmath</a><br>
| <a href="http://stuf.fedorapeople.org" rel="noreferrer" target="_blank">stuf.fedorapeople.org</a>%2Ffortran-modules%2Ffortran-<br>
| modules.html&amp;data=02%7C01%7Cgdr%<a href="http://40microsoft.com" rel="noreferrer" target="_blank">40microsoft.com</a>%7Cd49f0fb63<br>
| aac4ce886ff08d68dddd8b0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7<br>
| C1%7C636852381303060160&amp;sdata=ltkTtPf84tUk76Am5swiz6eNBGqZW<br>
| ydRfDoswsYEmlA%3D&amp;reserved=0<br>
| <br>
| Feedback welcome.<br>
| <br>
| Thanks,<br>
| <br>
| --Ben<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" rel="noreferrer" target="_blank">https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww</a>.<br>
| open-<br>
| <a href="http://std.org" rel="noreferrer" target="_blank">std.org</a>%2Fmailman%2Flistinfo%2Ftooling&amp;data=02%7C01%7Cgdr%40m<br>
| <a href="http://icrosoft.com" rel="noreferrer" target="_blank">icrosoft.com</a>%7Cd49f0fb63aac4ce886ff08d68dddd8b0%7C72f988bf86f141af9<br>
| 1ab2d7cd011db47%7C1%7C1%7C636852381303060160&amp;sdata=YLene6t<br>
| qdjuV7ad%2BAHf5kceett%2F1Whqj7Db0zka470g%3D&amp;reserved=0<br>
_______________________________________________<br>
Ext mailing list<br>
<a href="mailto:Ext@lists.isocpp.org" target="_blank">Ext@lists.isocpp.org</a><br>
Subscription: <a href="http://lists.isocpp.org/mailman/listinfo.cgi/ext" rel="noreferrer" target="_blank">http://lists.isocpp.org/mailman/listinfo.cgi/ext</a><br>
Link to this post: <a href="http://lists.isocpp.org/ext/2019/02/7507.php" rel="noreferrer" target="_blank">http://lists.isocpp.org/ext/2019/02/7507.php</a><br>
</blockquote></div>