Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: Mars lander crash
Date: Sun, 11 Dec 2016 18:29:14 -0800
Organization: None to speak of
Lines: 54
Message-ID: <lnpokxsww5.fsf@kst-u.example.com>
References: <o2e7s1$ea6$1@dont-email.me> <o2e8sg$hp7$1@dont-email.me> <o2ecu8$v73$1@dont-email.me> <o2eel2$614$1@dont-email.me> <o2eg20$b90$1@dont-email.me> <o2emds$5ek$1@dont-email.me> <o2epuf$juu$1@dont-email.me> <o2es0l$sea$1@dont-email.me> <o2jgbu$ih7$1@dont-email.me> <0ada6074-e2fb-48ab-b244-db84e2449e26@googlegroups.com> <o2k3od$7bu$1@dont-email.me> <lntwaategy.fsf@kst-u.example.com> <o2kib1$oki$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: mx02.eternal-september.org; posting-host="5ae493c5c0eddd0692ad00c7942bf15f"; logging-data="27278"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/tPQ8Pk/D2TrIvbKsUVibq"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:3ZbWLQW169/sNsn5MOpwsSw93Ow= sha1:NW+7THiAuKBNFTcJ2cTQLvihSSQ=
Xref: csiph.com comp.lang.c:98970

jacobnavia <jacob@jacob.remcomp.fr> writes:
> Le 11/12/2016 à 21:09, Keith Thompson a écrit :

jacob, some or all of your articles have this header line:

Content-Type: text/plain; charset=windows-1252; format=flowed

The system I use doesn't handle that correctly, causing the words "à"
and "écrit" to be displayed incorrectly.  Is there any way you can
configure your newsreader to post using UTF-8?

>> jacobnavia <jacob@jacob.remcomp.fr> writes:
[...]
>>> In any case I will modify lcc-win to generate SIGFPE instead of
>>> branching to an ad-hoc routine.
>>
>> Sure, but the FPE in SIGFPE stands for "floating point exception".
>
> Who knows?
>
> It could be Final Point before Exit, Full Program Error, Freak Problem 
> Encountered, even False Prejudices lead to Errors, isn't it?
>
> :-)

No, I'm reasonably sure it stands for floating-point exception.  But my
conclusions based on that were incorrect.

Quoting the C99 Rationale:

    The signal machinery contains many misnomers: SIGFPE, SIGILL,
    and SIGSEGV have their roots in PDP-11 hardware terminology, but
    the names are too entrenched to change. The occurrence of SIGFPE,
    for instance, does not necessarily indicate a floating-point
    error. A conforming implementation is not required to field
    any hardware interrupts.

And as James Kuyper points out, POSIX allows (but does not require)
SIGFPE to be raised for integer errors.

[...]

>> Just for the sake of clarity, you might consider defining a separate
>> signal for integer overflow and divide by zero.

I withdraw that suggestion.

[...]

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"