Re: Clarification for interface specification "C11 threads.h"
>> I am curious if you will get feedback by standardisation committee members
>> for your descriptions.
>> Did you forward any of them to an "official" communication channel?
> I am not sure what channel that would be, the ISO committees
> don't seem to be very open to the outside world.
Do you get also any useful information by Derek M. Jones occasionally? ;-)
> Generally, if you look at the text for free that you are citing,
> and compare it with the text about the threads in C11, you'll notice
> a difference in quality. C11 certainly lacked some iterations
> of discussion and error correction before it went into the standard.
> In particular, a better coordination with the POSIX committee
> would have been in order concerning threads.
I see also another update candidate if you compare descriptions for the
functions "pthread_cond_wait" and "cnd_wait".
When using condition variables there is always a Boolean predicate involving
shared variables associated with each condition wait that is true if the thread
should proceed. Spurious wakeups from the pthread_cond_timedwait() or
pthread_cond_wait() functions may occur.
Since the return from pthread_cond_timedwait() or pthread_cond_wait() does not
imply anything about the value of this predicate, the predicate should be
re-evaluated upon such return.
How do you think about further clarification for the handling of "predicates"
and "spurious wakeups" by the current standard specification for the C
Do you need not to care for them eventually because they are not mentioned in a
corresponding draft document?
|All times are GMT. The time now is 11:48 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.