Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.std.c,comp.lang.c Subject: Re: The threading specs in the standard: a new catastrophe Date: Fri, 08 Jul 2011 23:52:36 +1200 Lines: 27 Message-ID: <97o9diF6tbU6@mid.individual.net> References: <97nhr2F6tbU3@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 1cy9oNzxSA/0uwkveSTRrATxb3+V44rh8sURGArw/iqve2k3zW Cancel-Lock: sha1:T4+yzo8PpDQ13EZAVpdZe78zjoY= User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.9) Gecko/20101021 Lightning/1.0b2 Thunderbird/3.1.4 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.std.c:652 comp.lang.c:7959 On 07/ 8/11 11:46 PM, James Kuyper wrote: > On 07/08/2011 01:10 AM, Ian Collins wrote: >> On 07/ 7/11 10:33 PM, jacob navia wrote: > .... >>> 7.25.1.4 >>> cnd_t >>> which is a complete object type that holds an identifier for a >>> condition variable; >>> >>> How can a type "hold an identifier" ??? The committee defines in >>> 6.4.2.1.2 an identifier as a sequence of letters that designates >>> one or more entities. >>> Now, we have the opposite: a type holds an identifier and nowhere >>> is explained what that should mean! >> >> The type is an implementation detail, just like pthread_t is in POSIX. > > Even if it's an implementation detail, it's description should still be > meaningful in the standard; "hold an identifier" doesn't satisfy that > requirement. Well the SUS describes pthread_t as a type "Used to identify a thread" and pthread_cond_t as a type "Used for condition variables". It qualify them as types that are not required to be arithmetic types, but that's all. -- Ian Collins