C++ Logo


Advanced search

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

From: Boris Kolpackov <boris_at_[hidden]>
Date: Wed, 6 Mar 2019 14:54:52 +0200
Gabriel Dos Reis via Modules <modules_at_[hidden]> writes:

> > On Mar 5, 2019, at 8:29 AM, Ben Boeckel <ben.boeckel_at_[hidden]> wrote:
> >
> > Is it feasible for scanning to not do that and instead load it as if it
> > were `#include` and dropping non-exported macros at the end of the
> > import?
> That is exactly what I would expect, and what we talked about on the
> first telecon. Especially for matters such as finding macros that are
> made available by a header unit import.

Wouldn't that also require that importing TU's macros be dropped before
preprocessing (each) header unit's "real header"?

Received on 2019-03-06 13:54:59