On Wed, Jan 05, 2000 at 10:51:01AM +0000, Steve Papacharalambous wrote:
> The only comments that I have are with the thread specific calls. The
> use of the word "pthread" implies POSIX compliance and should not be
> used unless they are standard POSIX API calls. Why not use something
> like task or thread, which would avoid any possible confusion, for
> example:
RTLinux pthreads conform to the POSIX standards except where _np is
suffixed to indicate "non portable" (as is requested in the standard).
BTW: pthread_suspend(thread_t) is part of the x/open extension to
POSIX.
> int rtl_thread_suspend(rtl_thread_t * thread);
>
> Also, why not start with the NMTv1/RTAI api and derive a common subset?
>
> Best regards,
>
> Steve
>
> --- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> ----
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/~rtlinux/
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
