Last update: 23 February,1998
Eastwood #7 _____________________________________________________________________________ Topic: visibility of symbols part 2 Relevant Sections: pthread.h Spec: XSH Issue 5 Resolution Request: ------------------- Taking a function such as pthread_attr_setscope(), for example, 9945-1:1996, p300, 13.5.1.2 states: If _POSIX_THREAD_PRIORITY_SCHEDULING is defined: requirements are listed . . Otherwise: Either the implementation shall support the pthread_attr_setscope function as described above, or the function shall not be provided. (The shall not be provided allows ISO 9945-1:1996 systems not even to provide stubs - thus accomodating .1-90 systems ) Then section 13.5.1.4 specifies a permitted return value of ENOSYS when the implementation does not support the pthread_attr_setscope() function. I'm probably being legalistic here, but: Is a system which defines _POSIX_THREAD_PRIORITY_SCHEDULING and provides an implementation of pthread_attr_setscope() which always returns ENOSYS conformant ? Is a system which does NOT define _POSIX_THREAD_PRIORITY_SCHEDULING and provides an implementation of pthread_attr_setscope() which always returns ENOSYS conformant ? Is a system which does NOT define _POSIX_THREAD_PRIORITY_SCHEDULING and provides an implementation of pthread_attr_setscope() which meets the requirements specified in 13.5.1.2 9945-1:1996 conformant ? Does the ENOSYS return value exist because the provision of the _POSIX_THREAD_PRIORITY_SCHEDULING feature may be run-time dependent (available at times and unavailable at others) ? Resolution Response ------------------- Forwarded to the PASC 1003.1c Interpretations Committee. as PASC P1003.1c #43. Rationale ------------- None. Forwarded to Base group: Dec 11 1996 Approved: Feb 1998