private:
- thread_info *m_thread;
+ /* Use the "class" keyword here, because of a class with a
"thread_info"
+ function in the Darwin API. */
+ class thread_info *m_thread;
This comment sounds incorrect. A a "thread_info" function/method
inside some class couldn't possibly interfere, right? The issue is
that there's a _free-function_ called thread_info, right?
Err yeah, the "class with a" part should not be there:
+ /* Use the "class" keyword here, because of a "thread_info"
+ function in the Darwin API. */