Date: Mon, 27 Nov 2000 08:45:50 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: DJ Delorie <dj AT delorie DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: New patch for dtou.c
In-Reply-To: <200011262148.QAA21577@envy.delorie.com>
Message-ID: <Pine.SUN.3.91.1001127084534.15394H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 26 Nov 2000, DJ Delorie wrote:

> dtou should return zero if it was successful.  "Successful" means it
> changed the files it should have, and left the files it should have.
> A non-success exit (nonzero) should be restricted to *unexpected*
> problems, such as file not found, disk full, access denied. read-only
> media, etc.
> 
> My preference is that the exit code should reflect the number of
> problems encountered, not the type.

I think the final version committed to the CVS works like this, for
compatibility with previous versions (since `dtou' is used in
Makefile's of some ported packages).

What I suggested was meant to allow use of `dtou' as a kind of
file-type detection program.  However, the fact that `dtou' can work
on many files makes it difficult to implement this in a reasonable
way.