On 2016-02-26 04:24, Igor Baidiuk wrote:
> To me, module proposal can actually handle this. A compiler smart enough
> can extract "public layer" from module definition and recompile dependents
> only when that public layer is changed. And please note that that public
> layer will also include at least size of private part. Something like
> `private: char _1234__[PRIVATE_PART_SIZE];`

How do modules work from a build system perspective, anyway? Does the
compiler write out some new type of object file that becomes an input
for files using those modules? (In particular, how does the build tool
know when it needs to reinvoke the compiler for a particular source
file, once modules are thrown into the mix?)

Do you expect the compiler to be sufficiently clever as to not overwrite
an existing compiled module file if the one it just produced has the
same contents?

Or is the compiler expected to replace build tools entirely, i.e. to
build a library, you invoke the compiler once, passing it *every source
file used*, and expect the compiler to sort out what needs to be done?

--
Matthew

--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-proposals@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/napq98%24db2%241%40ger.gmane.org.

.