Curtis Dyer a écrit :
This doesn't seem to be at all the case. If you take a look at the
N1425 draft, you'll see there are many significant changes,
including the support for threading.
I posted an article about the threading proposal in comp.std.c.
It is basically the documentation of a threading library of
Plauger.
Yes, it is a good idea, but there are still thousands of things to do
first.
o The library is an unchanged copy of the C library of 1980. Using
the same software today after 30 years of development (and what a
development) in this field is plain nonsense. Many proposals have
been done to update the C library, specifically to correct the obvious
lack of security and error handling. Yes, the committee got rid of
gets() (could have been done in 1999) and acknowledged the buffer
overflow in the asctime() code, but still, there are a LOT of
functions in the standard library, specially the string handling
functions that are plainly WRONG...
How can we keep strtok and be multi-threading at the same time?
I did not see any update for multi-threading in the fopen/fclose
and all the functions of the standard library.
o There is no standard way of making a list/a tree/ a flexible array/
in C. Everything must be ported, recompiled, etc. I am working in
a proposalfor this, but apparently the committee will decide a
feature freeze next meeting, so I will have to wait till 2020
at least.
o I would like to know what is a "significant change" in the proposal.
I have seen a few detail changes but really nothing significant.
I could be wrong of course.