As I understand it, that's usually how major tooling innovations go between the two working groups. They get tested first in C++, and then (if they're very successful) they might trickle into C.
Well they *might* trickle down to C and usually very late. I think, by being stalled by the C++ committee he brought #embed to C first.
So it is a win for C programmers since they get the feature earlier and not something from C++ that *might* get copied into C years late.
Comments
So it is a win for C programmers since they get the feature earlier and not something from C++ that *might* get copied into C years late.