computer45
unread,Feb 15, 2018, 3:04:12 PM2/15/18You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to
Hello,
C++ is getting better , read this:
---
According to C++ modules proposal, from the very paper you cited, it's
the first of the three primary goals for adding modules:
1 Introduction
Modules are a mechanism to package libraries and encapsulate their
implementations. They differ from the traditional approach of
translation units and header files primarily in that all entities are
defined in just one place (even classes, templates, etc.). This paper
proposes a module mechanism (somewhat similar to that of Modula-2) with
three primary goals:
Significantly improve build times of large projects
Enable a better separation between interface and implementation
Provide a viable transition path for existing libraries While these are
the driving goals, the proposal also resolves a number of other
longstanding practical C++ issues (initialization ordering, run-time
performance, etc.).
Since header files are typically included in many other files, the growth
in build cycles is generally superlinear with respect to the total
amount of source code. If the issue is not addressed, it is likely to
become worse as the use of templates increases and more powerful
declarative facilities (like concepts, contract programming, etc.) are
added to the language.
Modules address this issue by replacing the textual inclusion mechanism
(whose processing time is roughly proportional to the amount of code
included) by a precompiled module attachment mechanism (whose processing
time—when properly implemented— is roughly proportional to the number of
imported declarations). The property that client translation units need
not be recompiled when private module definitions change can be retained.
---
Thank you,
Amine Moulay Ramdane.