|Did you know ...
Id is the alias name if the option
is given. Otherwise it is a blob of type
The anonymous blobs are subject to atom garbage collection. If a thread
handle is garbage collected and the thread is not detached, it
is joined if it has already terminated (see thread_join/2)
and detached otherwise (see thread_detach/1).196Up
to version 7.3.23, anonymous thread handles were integers. Using
integers did not allow for safe checking of the thread's status as the
thread may have died and the handle may have been reused and did not
allow for garbage collection to take care of forgotten threads.
The thread identifier blobs are printed as
where I is the internal thread identifier and Ptr
is the unique address of the identifier. The I is accepted as
input argument for all thread APIs that accept a thread identifier for
convenient interaction from the toplevel. See also thread_property/2.
Options is a list of options. The currently defined
options are below. Stack size options can also take the value
infinite, which is mapped to the maximum stack size
supported by the platform.
domain_error is raised. Referring to CPUs equal to or
higher than the known number of CPUs returns an
This option is currently implemented for systems that provide pthread_attr_setaffinity_np(). The option is silently ignored on other systems.bugThere is currently no way to discover whether this option is supported.
true), the new thread is created with the property
debug(false) and debugging is disabled before the new
thread is started. The thread debugging predicates such as tspy/1
do not signal threads with the debug property set to
the flag is only used as a hint for the various debugging primitives,
i.e., the system does not really enforce that the target thread stays in nodebug
false (default), the thread can be waited for using
must be called on this thread to reclaim all resources associated with
the thread. If
true, the system will reclaim all associated
resources automatically after the thread finishes. Please note that
thread identifiers are freed for reuse after a detached thread finishes
or a normal thread has been joined. See also thread_join/2
If a detached thread dies due to failure or exception of the initial goal, the thread prints a message using print_message/2. If such termination is considered normal, the code must be wrapped using ignore/1 and/or catch/3 to ensure successful completion.
__thread_pool_manager (see thread_create_in_pool/4),
which is created lazily, has a predictable state. The following
properties are inherited:
max_size(o)ption for details.
The Goal argument is copied to the new Prolog engine. This implies that further instantiation of this term in either thread does not have consequences for the other thread: Prolog threads do not share data from their stacks.