2 ms·
Unlikely to happen. This isn't "how do we rethink C", there are plenty of other, better places for that to happen. It's how do we make incremental improvement
by rwmj 8y ago
Unlikely to happen. This isn't "how do we rethink C", there are plenty of other, better places for that to happen. It's how do we make incremental improvements that benefit us, but remain in the spirit of C and compatible with the enormous existing body of code.
In fact there's a Charter describing it better than I can:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2086.htm http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2086.htm
- vkazanov 8y agoI read the Charter, yes. Now, how do those error-related proposals violate it? Such as: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2289.pdf http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2289.pdf It seems to be very delicate about being backwards-compatible.
- vkazanov 8y agoIn fact, I think WG14 was in favour if the N2289 proposal.