| To: | yyyyyyyyyyyyyyy@xxxxxxxxxxxxx |
|---|---|
| Subject: | Defect in XSH pthread_attr_getinheritsched |
| From: | yyyyyyyy@xxxxxxx |
| Date: | Mon, 11 Aug 2003 14:34:16 +0100 (BST) |
Defect report from : Loic Domaigne , Personal Interest
(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)
@ page 988 line 31518 section pthread_attr_getinheritsched comment
{pthread_attr_setinheritsched}
Problem:
Edition of Specification (Year): 2003
Defect code : 3. Clarification required
References are given against TC1.
At line 31518, the standard define a possible ENOTSUP error for
pthread_setinheritsched() when "an attempt was made to set the attribute
to an unsupported value."
As explained by David Butenhof on austin-group-l (Thr #5856):
| I think we ought to remove the ENOTSUP if we're cleaning up -- unless
| someone can recall why it was there and offer some rationale. ;-)
| PTHREAD_INHERIT_SCHED and PTHREAD_EXPLICIT_SCHED must be supported. So
| ENOTSUP could apply only to non-standard additional inheritsched
| codes. (And I still can't imagine how any could be reasonable and
| valid; but nevermind that.) This error code presupposes that it's OK
| for an implementation to define nonstandard codes that it doesn't
| support. Dumb. But even with that... the standard never precludes
| adding additional error codes for additional conditions not covered
| by the standard. Without extensions, or even with reasonable
| extensions, ENOTSUP has no purpose here.
Action:
remove the line 31518
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Defect in XSH pthread_attr_getstacksize, loic-dev |
|---|---|
| Next by Date: | Defect in XSH pthread_attr_getscope, loic-dev |
| Previous by Thread: | Defect in XSH pthread_attr_getinheritsched, loic-dev |
| Next by Thread: | Defect in XSH pthread_attr_getinheritsched, loic-dev |
| Indexes: | [Date] [Thread] [All Lists] |