From: Scott Schwartz schwartz@groucho.cse.psu.edu
Subject: expecting more from errstr
Date: Fri, 6 May 1994 20:32:19 -0400 [thread overview]
Message-ID: <19940507003219.rHf1-4lHZcT8LZCZVgBdc8K07wi5w21vmmhivUKDRlM@z> (raw)
Emboldened by the favorable reply to my last query, here is
another:
One annoying thing in Unix is when you say something like
open("/no/such/directory/or/file",0), it tells you that it something
doesn't exist, but doesn't say what, which sometimes makes for
uninformative error messages. Now that we have errstr, instead of just
errno, it would be delightful if it would encode something about
what went wrong, so that perror could say something like
open: failed because directory 'such' does not exist
reply other threads:[~1994-05-07 0:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19940507003219.rHf1-4lHZcT8LZCZVgBdc8K07wi5w21vmmhivUKDRlM@z \
--to=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).