From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri,  6 May 1994 20:32:19 -0400
From: Scott Schwartz schwartz@groucho.cse.psu.edu
Subject: expecting more from errstr
Topicbox-Message-UUID: 01e19d54-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19940507003219.rHf1-4lHZcT8LZCZVgBdc8K07wi5w21vmmhivUKDRlM@z>

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