From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <7ccb1b5dbf5f23fc0650cdf24510eb9d@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: Error reporting (Was: [9fans] GNU Make)
Date: Thu,  3 Jun 2004 17:18:59 +0100
From: rog@vitanuova.com
In-Reply-To: <67be9cab86bd47c174c4648830ecf38b@vitanuova.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 9438e036-eacd-11e9-9e20-41e7f4b1d025

> >>cannot allocate resource: '/x/y' does not exist
> 
> i'm not sure that was a good example.
> 
> especially in the APE context, and perhaps not just there,
> i'd have said that ENOENT was fine.  that's why it ultimately
> couldn't allocate the resource, and being the underlying error,
> could be regarded as the more important aspect or at least equally important
> in this case.

i was imagining this might happen when opening a "clone"
file for example. the error is not that the file itself does not
exist (it does) but that the thing serving the file encountered
an error when trying to open it. the text after the colon
describes the reason for that error (which happened to involve
another file '/x/y').

it would be misleading for APE to report ENOENT in this
case, i think.