>
> What’s unexpected to me is that changing a header whose contents are not
> usually visible may still require rebuilding all of my .cpp files.
> module Foo { module One { header “One.h” } module Two { header “Two.h” } }
>
> // One.cpp - I don’t want to rebuild when Two.h changes
> #import <Foo/One.h>
>
> Do we agree that this is unnecessary if submodules cannot accidentally be
> affected by changes in other submodules they don’t import (and we have some
> way to get the set of dependency files for just the submodule)?
>
> No, I don't agree with that. One.cpp might inline some function definitions
> from Two.h, for instance. Or it might fail to build because it declares
> something that conflicts with something in Two.h.
I feel like I”m missing something - how is that different from One.cpp having
conflicts with some completely different header or module that is not imported
into that particular TU?
Ben
_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
