[Tooling] [isocpp-modules] Dependency information for module-aware build tools
Boris Kolpackov
boris at codesynthesis.com
Wed Mar 6 13:54:52 CET 2019
Gabriel Dos Reis via Modules <modules at lists.isocpp.org> writes:
> > On Mar 5, 2019, at 8:29 AM, Ben Boeckel <ben.boeckel at kitware.com> 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"?
More information about the Tooling
mailing list