[openbeos] Re: odd code in expander
- From: Alan Westbrook <alan@xxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Mon, 19 Apr 2004 23:19:19 -0700
ok, explain why you are getting the thread_info, nothing is done with it.
and what about the other stuff?
=)
Alan
Jonas Sundstrom wrote:
Alan Westbrook <alan@xxxxxxxxxxxxxx> wrote:
...
status_t status = B_OK;
thread_info thread_info;
status = get_thread_info (fThreadId, &thread_info);
...
if (status == B_OK) {
...
1) using get_thread_info to see if the thread is
ok is susceptable to race conditions.
if (status == B_OK) doesn't test if the thread is ok,
but whether or not get_thread_info() was successful.
/Jonas Sundström. www.kirilla.com
- Follow-Ups:
- [openbeos] Re: odd code in expander
- From: Jonas Sundstrom
- References:
- [openbeos] Re: odd code in expander
- From: Jonas Sundstrom
Other related posts:
- » [openbeos] odd code in expander
- » [openbeos] Re: odd code in expander
- » [openbeos] Re: odd code in expander
- » [openbeos] Re: odd code in expander
- » [openbeos] Re: odd code in expander
- » [openbeos] Re: odd code in expander
Alan Westbrook <alan@xxxxxxxxxxxxxx> wrote: ...
status_t status = B_OK;
thread_info thread_info;
status = get_thread_info (fThreadId, &thread_info);
...
if (status == B_OK) {
...
1) using get_thread_info to see if the thread is ok is susceptable to race conditions.
if (status == B_OK) doesn't test if the thread is ok, but whether or not get_thread_info() was successful.
/Jonas Sundström. www.kirilla.com
- [openbeos] Re: odd code in expander
- From: Jonas Sundstrom
- [openbeos] Re: odd code in expander
- From: Jonas Sundstrom