From owner-freebsd-hackers  Sat Dec  2 13:49:14 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA26723
          for hackers-outgoing; Sat, 2 Dec 1995 13:49:14 -0800
Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id NAA26677
          for <hackers@freebsd.org>; Sat, 2 Dec 1995 13:48:56 -0800
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA28943
  (5.67a/IDA-1.5); Sat, 2 Dec 1995 07:49:16 -0600
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id HAA02084; Sat, 2 Dec 1995 07:47:00 -0600
Date: Sat, 2 Dec 1995 07:47:00 -0600
From: peter@taronga.com (Peter da Silva)
Message-Id: <199512021347.HAA02084@bonkers.taronga.com>
To: markd@grizzly.com
Subject: Re: NPX still broken in 2.1.0-951104-SNAP...
Newsgroups: taronga.freebsd.hackers
In-Reply-To: <199511060224.SAA06030@grizzly.com>
References: <199511052310.KAA18574@godzilla.zeta.org.au>
Organization: Taronga Park BBS
Cc: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
Precedence: bulk

Mark Diekhans  <markd@grizzly.com> wrote:
>Its incompatible with every Unix system I have access to.  See enclosed table.
>No system core dumps!  I don't have any standards handy, but SCO, which
>is X/Open, ANSI, and POSIX compatible sets errno and returns NaN.

I agree, this is the best default behaviour.

>Most portable software checks errno, although the best approach is to check
>both errno and NaN.

Doubled. You shouldn't check errno unless you have an error status. Too
much stuff sets errno as a side effect (:-p).