You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation on $Archive::Tar::WARN states that setting this variable to 0 is not threadsafe. That is not really accurate. It is threadsafe to set that variable to 0 as doing so only turns of a carp call. What is not threadsafe is to set this variable to 0, and then use the $Archive::Tar::error variable. However, it is threadsafe to set $Archive::Tar::WARN to 0 and use the $tar->error method to obtain error messages.
I know this is just quibbling on details, but if you want to catch warnings in a threadsafe manner, and don't want warnings handled by the current $SIG{__WARN__} handler, then setting this variable to 0 and using $tar->error is a threadsafe way to do so, and the documentation is misleading on this.
The text was updated successfully, but these errors were encountered:
The documentation on
$Archive::Tar::WARN
states that setting this variable to0
is not threadsafe. That is not really accurate. It is threadsafe to set that variable to0
as doing so only turns of acarp
call. What is not threadsafe is to set this variable to0
, and then use the$Archive::Tar::error
variable. However, it is threadsafe to set$Archive::Tar::WARN
to0
and use the$tar->error
method to obtain error messages.I know this is just quibbling on details, but if you want to catch warnings in a threadsafe manner, and don't want warnings handled by the current
$SIG{__WARN__}
handler, then setting this variable to0
and using$tar->error
is a threadsafe way to do so, and the documentation is misleading on this.The text was updated successfully, but these errors were encountered: