Re: Re: Perl Style: About error messges opening files

[flyingmoose]

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.

From perldoc POSIX:

    perror  This is identical to the C function "perror()", which outp
+uts to
            the standard error stream the specified message followed b
+y ": "
            and the current error string. Use the "warn()" function an
+d the
            "$!" 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.

[Abigail-II]

You said you were new to perror, so I'm just explaining why it exists in C.

Care to point out where I said I was new to perror? I'm not new to it, and I scrolling back in the thread, I can't find where I erroneously said I did.

Abigail

[flyingmoose]

quote:

I've been writing some C lately, and I've started appreciating perror.

[Abigail-II]

Where does that say I'm new to perror?

Abigail