From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] float.h
Date: Wed, 6 Aug 2008 08:43:05 -0400 [thread overview]
Message-ID: <3612518B-A55C-476F-B287-2B52C696014D@mac.com> (raw)
In-Reply-To: <84fe7a375cfada78925e89e61fa6774e@terzarima.net>
On Aug 6, 2008, at 4:06 AM, Charles Forsyth wrote:
>> My program uses some of them (DBL_MIN, DBL_MAX, DBL_EPSILON), and
>> including <ape/float.h> yields name clashes. Thanks.
>
>> #include <u.h>
>> ...
>> #include <ape/float.h>
>
> it's surprisingly important not to leave out important information,
> such as
> what important things were in the "..." (other include files) and,
> most importantly, the particular "name clashes".
>
> i'd noticed you were using <ape/float.h> not <float.h> which i'd
> thought curious
> (were you mixing APE and Plan 9 include files?) but like most others
> i'd initially
> assumed the "name clashes" had to do with the DBL_ names. odd.
>
Yes. Plan 9 has no float.h of its own.
> guessing that the "..." contained "#include <libc.h>" and trying a
> little test,
> I find that probably the "name clashes" were (was?) probably singular:
>
> /386/include/ape/float.h:43 yy.c:3 redeclare tag: FPdbleword
>
The other is in <u.h>.
> so now we know the problem, what to do about it?
> i know an unpleasant way but perhaps someone else can think of a
> good way to get those
> values outside the APE include files. libc.h doesn't define
> equivalents.
> perhaps the values aren't actually all that useful (i'm not sure how
> i'd use
> them myself in a calculator, for instance).
>
>
If your unpleasant way is to copy float.h, it won't work; you'll need
one for each $objtype. I found an algorithm to get epsilon, but not
min or max.
next prev parent reply other threads:[~2008-08-06 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 19:07 Pietro Gagliardi
2008-08-05 23:43 ` Russ Cox
2008-08-06 2:51 ` Pietro Gagliardi
2008-08-06 3:14 ` ron minnich
2008-08-06 3:22 ` Pietro Gagliardi
2008-08-06 8:06 ` Charles Forsyth
2008-08-06 12:43 ` Pietro Gagliardi [this message]
2008-08-06 12:59 ` erik quanstrom
2008-08-06 16:29 ` Greg Comeau
2008-08-07 18:24 ` Pietro Gagliardi
2008-08-07 19:49 ` Federico G. Benavento
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=3612518B-A55C-476F-B287-2B52C696014D@mac.com \
--to=pietro10@mac.com \
--cc=9fans@9fans.net \
/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).