I simply printed a brand new doc on the WG14 (C committee) website
It’s try to push the fast-forward button to the annoyingly gradual growth course of for C and its coordination with C++.
The C and C++ programming languages have advanced from a typical
ancestor a few years in the past and have all the time been developed in retaining an in depth eye on one another. Each accountable committees, WG14 and WG21, have all the time sought each languages to be suitable so far as appeared doable; on a binary stage for mutual linkage of software program parts, and on a source-header stage for mutual entry to the so linked parts. Nonetheless, gratuitous incompatibilities have crept into them, and cross-language programming is these days fairly troublesome to realize and nearly unimaginable to show.
On the optimistic facet, in recent times the efforts to bridge the hole between the 2 language have been renewed and several other fruitful initiatives have been undertaken to unify the approaches in a number of domains. These concern particularly atomic sorts and operations, signal representations of integers, the reminiscence mannequin(s), and the attribute function.
This specification is an try to strengthen these dynamics and to formulate a typical language core that ideally could be built-in in each languages and would offer a strong base for the long run growth of each, and, that will be a lot less complicated to make use of, to grasp and to implement. It’s oriented to keep up and lengthen some principal traits which might be already current within the intersection:
- Sturdy static typing
This frequent core provides options to each languages, and thus it has not but an entire implementation. Nonetheless, first experiments present that it shouldn’t be very difficult to offer reference implementations inside compiler frameworks that have already got front-ends for each languages, and that thus have already got a lot of the options in a method or one other.