From 2bda80fcb9f537f2b7a2d7e8df150823199b713b Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Fri, 31 Dec 2004 22:41:32 +0000 Subject: [PATCH] Typographic fixes. --- doc/threads.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/threads.texi b/doc/threads.texi index ac9ccd4..af84ffe 100644 --- a/doc/threads.texi +++ b/doc/threads.texi @@ -429,8 +429,8 @@ Incidentally, we don't use @code{struct thread *} as @func{thread_join}'s parameter type because a thread pointer is not unique over time. That is, when a thread dies, its memory may be, whether immediately or much later, reused for another thread. If -thread A over time had two children B and C that were stored at the -same address, then @code{thread_join(@var{B})} and +thread @var{A} over time had two children @var{B} and @var{C} that +were stored at the same address, then @code{thread_join(@var{B})} and @code{thread_join(@var{C})} would be ambiguous. Introducing a thread id or @dfn{tid}, represented by type @code{tid_t}, that is intentionally unique over time solves the problem. The provided code -- 2.30.2