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: Wojtek Lerch <wojtek_l@yahoo.ca>
Newsgroups: comp.std.c,comp.lang.c
Subject: Re: The threading specs in the standard: a new catastrophe
Date: Thu, 07 Jul 2011 12:31:22 -0400
Lines: 23
Message-ID: <97m59uF1nsU1@mid.individual.net>
References: <iv422a$33k$1@speranza.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net NF5O6I6gjjVV/oFG8o10nwUdKd5RnAIQ2n7SgKHBXRMSqi/9BG
Cancel-Lock: sha1:E22mXoGLK06HzuMrjlENZgvPcyc=
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
In-Reply-To: <iv422a$33k$1@speranza.aioe.org>
Xref: x330-a1.tempe.blueboxinc.net comp.std.c:611 comp.lang.c:7853

On 07/07/2011 6:33 AM, jacob navia wrote:
...
> 2) The proposed functions are absurd.
>
> Take, for instance, nothing less than the thread creation function
> thrd_create:
>
> int thrd_create(thrd_t *thr, thrd_start_t func,void *arg);
>
> As you can see, there are *no arguments that can be passed to the
> underlying operating system* to further specify the newly created
> thread. (The "args" arument is an argument for the thread).
>
> The pthreads standard (POSIX) proposes an "attributes" argument. The
> Microsoft threads propose a "security attributes" and a set of flags
> that further specify the newly created thread. The C API proposes
> NOTHING so it is impossible to use.

Do you find fopen() absurd and impossible to use too?  Or are file or 
stream attributes (such as the POSIX permission bits, or O_EXCL) less 
important to you than some of the thread attributes that POSIX or 
Windows have?