C++ Logo


Advanced search

Re: [Tooling] [Ext] Modules and tooling: Resolving module import declarations

From: Gabriel Dos Reis <gdr_at_[hidden]>
Date: Sat, 1 Sep 2018 00:08:35 +0000
An IDE does not necessarily build an artifact in the conventional sense. Yet, it needs to know the set of configuration parameters in order to understand the content of a source file.

— Gaby

> On Aug 31, 2018, at 11:14 AM, Nathan Sidwell <nathan_at_acm.org> wrote:
>> On 08/31/2018 12:05 PM, Tom Honermann wrote:
>> If so, my concern with that approach is that it effectively requires a build system.
> Let me clarify something here, it provides mechanism without policy, so yes, it requires something to give the policy. That is a build system. What we're discussing here is a build system -- how things get built. #includes and their include path are a build system in that respect.
> What the mapper does is decouple the compiler from whatever that build system is. (Unlike #include paths, which are baked into compilers.)
> nathan
> --
> Nathan Sidwell
> _______________________________________________
> Ext mailing list
> Ext_at_[hidden]
> Subscription: http://lists.isocpp.org/mailman/listinfo.cgi/ext
> Link to this post: http://lists.isocpp.org/ext/2018/08/5716.php

Received on 2018-09-01 02:08:40