From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: System calls without error checks in w32
Date: Sun, 30 May 2010 06:02:40 +0300 [thread overview]
Message-ID: <83k4qmt7lb.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTikCYomvvT9xSi7uAWdxa4utImKwq3BQVWT-fVCd@mail.gmail.com>
> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Sat, 29 May 2010 23:30:21 +0200
> Cc: emacs-devel@gnu.org
>
> On Sat, May 29, 2010 at 11:25 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> From: Lennart Borgman <lennart.borgman@gmail.com>
> >> Date: Sat, 29 May 2010 22:02:24 +0200
> >> Cc: emacs-devel@gnu.org
> >>
> >> > If you can suggest what to do when any of these fails, please do.
> >>
> >>
> >> I have already made the suggestion below.
> >
> > How in the world outputting an error message would help here?
>
> You mean instead of fixing the error directly? It is just a first step
> of course.
>
> The error message might also be interesting in itself. It can for
> example tell about resources lack etc. The API descriptions does not
> always tell the whole story.
Checking values returned by system calls is necessary to avoid working
with invalid objects returned by a failed system call. I thought you
were talking about this.
But it turns out you are talking about something else altogether: how
to debug possible failures in some APIs. That is a different story
and it requires different solutions. Please take a look at xdisp.c
and friends, which have special debugging code inside
#ifdef GLYPH_DEBUG.
In any case, the solution you suggest is not a good one, because it
obfuscates the source code and makes it harder to read and understand.
next prev parent reply other threads:[~2010-05-30 3:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 2:38 System calls without error checks in w32 Lennart Borgman
2010-05-29 17:43 ` Eli Zaretskii
2010-05-29 18:42 ` Lennart Borgman
2010-05-29 19:35 ` Eli Zaretskii
2010-05-29 20:02 ` Lennart Borgman
2010-05-29 21:25 ` Eli Zaretskii
2010-05-29 21:30 ` Lennart Borgman
2010-05-30 3:02 ` Eli Zaretskii [this message]
2010-05-30 3:26 ` Lennart Borgman
2010-05-30 17:36 ` Eli Zaretskii
2010-05-30 18:02 ` Lennart Borgman
2010-05-30 19:24 ` Juanma Barranquero
2010-05-30 22:37 ` Lennart Borgman
2010-05-30 23:03 ` Juanma Barranquero
2010-05-30 23:28 ` Lennart Borgman
2010-05-31 0:10 ` Juanma Barranquero
2010-05-31 0:58 ` Lennart Borgman
2010-05-31 2:02 ` Juanma Barranquero
2010-05-31 2:36 ` Lennart Borgman
2010-05-31 3:06 ` Juanma Barranquero
2010-05-31 3:05 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2010-05-31 9:18 grischka
2010-06-05 17:15 ` Jason Rumney
2010-06-07 10:37 ` grischka
2010-06-07 14:54 ` Stephen J. Turnbull
2010-06-07 15:23 ` Lennart Borgman
2010-06-07 17:21 ` grischka
2010-06-07 17:30 ` Lennart Borgman
2010-06-07 18:54 ` grischka
2010-06-08 0:32 ` Lennart Borgman
2010-06-08 0:34 ` Lennart Borgman
2010-06-07 19:56 ` Stefan Monnier
2010-06-07 23:35 ` Lennart Borgman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k4qmt7lb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).