Improved documentation of the thread_at_exit/1 predicate with a reference to the alternative at_exit/1 option of the thread_create/3 predicate.

git-svn-id: https://yap.svn.sf.net/svnroot/yap/trunk@2194 b08c6af1-5177-4d33-ba66-4b1c6b8b522a
This commit is contained in:
pmoura 2008-04-02 23:08:36 +00:00
parent 48e8101a87
commit 59d82a0fca

View File

@ -7778,8 +7778,7 @@ this flag is @code{off}.
@item max_workers @item max_workers
@findex max_workers (yap_flag/2 option) @findex max_workers (yap_flag/2 option)
@* Read-only flag telling the maximum number of Prolog workers when using @* Read-only flag telling the maximum number of parallel processes.
or-parallelism.
@item max_threads @item max_threads
@findex max_threads (yap_flag/2 option) @findex max_threads (yap_flag/2 option)
@ -12257,8 +12256,11 @@ Run @var{Goal} just before releasing the thread resources. This is to
be compared to @code{at_halt/1}, but only for the current be compared to @code{at_halt/1}, but only for the current
thread. These hooks are ran regardless of why the execution of the thread. These hooks are ran regardless of why the execution of the
thread has been completed. As these hooks are run, the return-code is thread has been completed. As these hooks are run, the return-code is
already available through @code{current_thread/2} using the result of already available through @code{thread_property/2} using the result of
@code{thread_self/1} as thread-identifier. @code{thread_self/1} as thread-identifier. If you want to guarantee the
execution of an exit hook no matter how the thread terminates (the thread
can be aborted before reaching the @code{thread_at_exit/1} call), consider
using instead the @code{at_exit/1} option of @code{thread_create/3}.
@item thread_setconcurrency(+@var{Old}, -@var{New}) @item thread_setconcurrency(+@var{Old}, -@var{New})
@findex thread_setconcurrency/2 @findex thread_setconcurrency/2