From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] fp stack overflow -- hypot
Date: Sat, 6 Mar 2004 21:24:35 +1100 [thread overview]
Message-ID: <01f601c40367$e64a2470$8201a8c0@cc77109e> (raw)
In-Reply-To: <5d2199bf9053e87c62827a04a630fe86@terzarima.net>
right on that charles, yes the reason that -A is needed to
make ape/cc ANSI has to do with all the crap code
that has to be compiled with it.
anyone gonna conjecture why the ape hypot is not as
good as the libc one ... can it just be preplaced?
(prototype issues aside.)
brucee
----- Original Message -----
From: "Charles Forsyth" <forsyth@terzarima.net>
To: <9fans@cse.psu.edu>
Sent: Friday, March 05, 2004 6:32 AM
Subject: Re: [9fans] fp stack overflow -- hypot
> >>I just didn't realize that, unlike pcc, cc does not issue warnings
> >>by default.
>
> no, presumably because too many old programs lacked prototypes,
> which indeed they did.
> -A stops it turning the checking off.
next prev parent reply other threads:[~2004-03-06 10:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 22:18 David Tolpin
2004-03-04 23:08 ` Bruce Ellis
2004-03-04 23:10 ` boyd, rounin
2004-03-04 23:53 ` Bruce Ellis
2004-03-04 23:54 ` David Tolpin
2004-03-05 6:32 ` Charles Forsyth
2004-03-06 10:24 ` Bruce Ellis [this message]
2004-03-05 12:13 Trickey, Howard W (Howard)
2004-03-05 12:19 ` boyd, rounin
2004-03-05 12:24 ` Gorka Guardiola Múzquiz
2004-03-05 12:30 ` boyd, rounin
2004-03-05 12:36 ` Gorka Guardiola Múzquiz
2004-03-05 12:38 ` Fco.J.Ballesteros
2004-03-05 12:49 ` boyd, rounin
2004-03-05 12:46 ` boyd, rounin
2004-03-05 12:24 ` David Tolpin
2004-03-05 12:37 ` boyd, rounin
2004-03-05 15:14 ` a
2004-03-05 15:25 ` boyd, rounin
2004-03-08 10:14 ` Douglas A. Gwyn
2004-03-08 10:59 ` Bruce Ellis
2004-03-09 9:47 ` Douglas A. Gwyn
2004-03-09 12:19 ` boyd, rounin
2004-03-09 22:58 ` Bruce Ellis
2004-03-11 9:38 ` Douglas A. Gwyn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='01f601c40367$e64a2470$8201a8c0@cc77109e' \
--to=brucee@chunder.com \
--cc=9fans@cse.psu.edu \
/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.
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 NNTP newsgroup(s).