[Tooling] [isocpp-modules] Dependency information for module-aware build tools

Gabriel Dos Reis gdr at microsoft.com
Tue Mar 5 06:10:54 CET 2019


What would be a “legacy” audience here, specifically?

— Gaby

On Mar 4, 2019, at 4:58 PM, Rene Rivera <grafikrobot at gmail.com<mailto:grafikrobot at gmail.com>> wrote:

On Mon, Mar 4, 2019 at 7:25 PM Gabriel Dos Reis via Modules <modules at lists.isocpp.org<mailto:modules at lists.isocpp.org>> wrote:
The search path facility is there only for “convenience”, for quick-and-dirty examples: the recommended approach is to explicitly list the mapping providing the IFC for the modules.  I continue to believe that is the right approach - but would love to be proven wrong.

It's best to investigate and test the various approaches not just your ideal. Depending on particular use cases one may be more appropriate than others. The TR needs to consider both the "legacy" and "future" audiences.

--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net<https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Frobot-dreams.net%2F&data=02%7C01%7Cgdr%40microsoft.com%7C99f8ce2afb064100452608d6a1167657%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636873515188269178&sdata=PZTRrKsGGosIMSvin%2F%2FkjJB%2BN9GQtOGkqwGAThBVL9g%3D&reserved=0>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.open-std.org/pipermail/tooling/attachments/20190305/fce26441/attachment.html 


More information about the Tooling mailing list