[550] in Pthreads mailing list archive
non-standard functions
daemon@ATHENA.MIT.EDU (Cheryl Huntington)
Wed Jan 22 19:39:14 1997
Date: Wed, 22 Jan 1997 16:26:19 -0800
From: Cheryl Huntington <clh@swdc.stratus.com>
To: pthreads@MIT.EDU
Cc: clh@swdc.stratus.com
I have found the following functions defined in this implementation
which are not defined in the finalized POSIX standard. Is this because
the implementation is based on an earlier draft? A lot of them are
clearly used within the library, but are they intended to be callable by
applications? If not, isn't is standard to prefix internal functions
names with "_"? I'm not intending to be critical, just trying to
understand their purpose.
pthread_cond_is_debug()
pthread_dump_state()
pthread_dump_info_to_file()
pthread_dump_info()
pthread_mutex_is_debug()
pthread_mutexattr_gettype()
pthread_attr_setcleanup()
pthread_attr_getfloatstate()
pthread_attr_setfloatstate()
pthread_init()
pthread_cleanupspecific()
pthread_key_allocate_data()
pthread_prio_queue_init()
pthread_prio_queue_deq()
pthread_prio_queue_remove()
pthread_yield()
pthread_queue_init()
pthread_queue_enq()
pthread_queue_get()
pthread_queue_deq()
pthread_queue_remove()
pthread_llist_remove()
pthread_sched_other_resume()
pthread_resched_resume()
pthread_sched_resume()
pthread_sched_prevent()
pthread_setup_siginfo()
pthread_sig_register()
pthread_sig_default()
pthread_sig_process()
pthread_signal()
pthread_sigprocmask()
pthread_atexit_inited()
pthread_atexit_add()
pthread_atexit_remove()
pthread_attr_destroy_nrv()
pthread_tad_count()
pthread_tad_done()
pthread_tad_start()
pthread_tad_create()
pthread_tad_wait()
pthread_tad_init()
pthread_tad_destroy()
--
Cheryl Huntington clh@swdc.stratus.com 408.559.5665
Stratus Western Development Center, Commands and Utilities Group
