Am 06.02.26 um 1:11 PM schrieb Daniel Kral: > On Fri Feb 6, 2026 at 11:24 AM CET, Fiona Ebner wrote: >> Am 04.02.26 um 10:17 AM schrieb Daniel Kral: >>> Otherwise, if the underlying detect_architecture(...) method returns any >>> false value, the return value of the call to protected_call(...) will >> >> Do you mean undef value here? If I return 0 inside a protected call I get 0 >> >>> return an empty string. >> >> not an empty string. >> >> There seems to be a difference in behavior between being in a nested >> protected call, which will return the result from the $sub directly, and >> a non-nested protected call, which reads the result from the pipe, which >> also results in an empty string when the result from $sub is undef. > > Good catch, thanks! I only tried it with non-nested protected calls > which use the output from the pipe and also assumed that the empty > string comes from the conversion from a falsy value to a string in perl, > which is the empty string.
Nit: should probably read "from a falsy value that does convert to an empty string in Perl". Not all falsy values do ;)
