From: Weiqi Gao <weiqigao AT a DOT crl DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Do Error Messages Really Help?
Date: Tue, 24 Aug 1999 19:17:31 -0500
Organization: CRL Network Services
Lines: 24
Message-ID: <37C3361B.C6E3ECB8@a.crl.com>
References: <199908232202 DOT SAA12175 AT delorie DOT com> <pJvw3.4742$ei1 DOT 9960 AT newsfeeds DOT bigpond DOT com> <7pu789$975 AT tandem DOT CAM DOT ORG>
NNTP-Posting-Host: a116007.stl1.as.crl.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i586)
X-Accept-Language: en
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Martin Peach wrote:
> 
> It sure would be useful to have stuff like ENOENT written out in long, I
> keep trying to guess what it might possibly stand for.
> "Error no Entry"? "Eno ain't here?" "Exit not Entrance?"  Surely there is
> not a DOS-like (8.3) limit on symbolic names?

That's where the documentation comes in.  Ever heard of it? the
documentation?  Thoese *d.zip archives?  Those are meant to be read by
the programmer.

Not everything can be explained in an intuitive way.  No matter how hard
you try, their is always someone who don't understand.  It is not the
compiler's job to teach.  To compiler compiles programs written by
programmers.  And the programmer is assumed to have some level of
understanding of how it works, including the meaning of ENOENT.

The GNU C library documentation is actually quite a pleasant read.  The
edition that I have has a section that explains all the error codes, up
to "EIOIO -- Go home and have a glass of dairy-fresh milk."

--
Weiqi Gao
weiqigao AT a DOT crl DOT com