Of course not... just saying that errno varies with each C function and a PITA to translate, so that is why perror() exists. "$!" is already nicely doing the work for us, hence no need for a Perl perror.
in reply to Re: Perl Style: About error messges opening files
in thread Perl Style: About error messges opening files
From perldoc POSIX:
perror This is identical to the C function "perror()", which outp
the standard error stream the specified message followed b
+y ": "
and the current error string. Use the "warn()" function an
"$!" variable instead, see the warn entry in the perlfunc
manpage and the section on "$ERRNO" in the perlvar manpage
You said you were new to perror, so I'm just explaining why it exists in C.