Lines Matching defs:exit

46         if ($sym =~ /^(?:stack|exit)/i) {
87 sub exit
97         Carp::croak('Usage: threads->exit(status)');
101     CORE::exit($status);
153                  'exit' => 'threads_only',
212                                 'exit'       => 'thread_only' },
230     threads->exit();
463 =item threads->exit()
466 C<threads-E<gt>exit()>.  This will cause the thread to return C<undef> in a
469 When called from the I<main> thread, this behaves the same as C<exit(0)>.
471 =item threads->exit(status)
473 When called from a thread, this behaves like C<threads-E<gt>exit()> (i.e., the
474 exit status code is ignored).
476 When called from the I<main> thread, this behaves the same as C<exit(status)>.
480 Calling C<die()> in a thread indicates an abnormal exit for the thread.  Any
482 thread will exit with a warning message that will contain any arguments passed
485 =item exit(status)
487 Calling L<exit()|perlfunc/"exit EXPR"> inside a thread causes the whole
488 application to terminate.  Because of this, the use of C<exit()> inside
492 If C<exit()> really is needed, then consider using the following:
494     threads->exit() if threads->can('exit');   # Thread friendly
495     exit(status);
497 =item use threads 'exit' => 'threads_only'
499 This globally overrides the default behavior of calling C<exit()> inside a
501 C<threads-E<gt>exit()>.  In other words, with this setting, calling C<exit()>
509 =item threads->create({'exit' => 'thread_only'}, ...)
511 This overrides the default behavior of C<exit()> inside the newly created
516 This can be used to change the I<exit thread only> behavior for a thread after
517 it has been created.  With a I<true> argument, C<exit()> will cause only the
518 thread to exit.  With a I<false> argument, C<exit()> will terminate the
525 Class method for use inside a thread to change its own behavior for C<exit()>.
737         $SIG{'KILL'} = sub { threads->exit(); };
823 point function, or by using C<threads-E<gt>exit()>.  For example, the thread