delorie.com/archives/browse.cgi | search |
From: | Jason Green <mail AT jgreen4 DOT fsnet DOT co DOT uk> |
To: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
Cc: | lauras AT softhome DOT net, djgpp-workers AT delorie DOT com |
Subject: | Re: Symify fixes |
Date: | Thu, 31 Aug 2000 19:12:54 +0100 |
Message-ID: | <4j7tqskrvkecn18jfdi9vtpbo5skmm82ke@4ax.com> |
References: | <3b5rqskv9adg5lcc3p4nhg2doib859r3n8 AT 4ax DOT com> <Pine DOT SUN DOT 3 DOT 91 DOT 1000831074644 DOT 20860E-100000 AT is> |
In-Reply-To: | <Pine.SUN.3.91.1000831074644.20860E-100000@is> |
X-Mailer: | Forte Agent 1.7/32.534 |
MIME-Version: | 1.0 |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id OAA17453 |
Reply-To: | djgpp-workers AT delorie DOT com |
On Thu, 31 Aug 2000 07:47:13 +0300 (IDT), you wrote: > The portable way to check for errno is to set it to zero before the > call to a function, then see if it is still zero after the function > returns. Actually no, a system call can legally set errno even if no error occured. Portability isn't important for symify though. > > I don't see how it is possible to give more specific error messages, > > I meant to say that adding strerror will result in more specific error > messages. Saying "read error: Bad file descriptor" is more > informative than just "read error", IMHO. ok. -- [please cc all replies, thanks]
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |