in reply to Suppressing thread warnings
It's dumb that blasted message cannot be disabled! Same with the 'Free to wrong pool' developer diagnostic.
The simplest solution is:
use POSIX qw[ _exit ]; _exit( 123 );
But be aware that no destructors will be called, so if anything in your code requires cleanup, instigate it manually first. For example,
undef $objectNeedingCleanup; _exit( 123 );
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Suppressing thread warnings
by lennysan (Novice) on Oct 10, 2008 at 20:20 UTC | |
by BrowserUk (Patriarch) on Oct 10, 2008 at 21:16 UTC |