From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <84fe7a375cfada78925e89e61fa6774e@terzarima.net>
To: 9fans@9fans.net
From: Charles Forsyth <forsyth@terzarima.net>
Date: Wed,  6 Aug 2008 09:06:40 +0100
In-Reply-To: <A34E0AEF-930F-45D3-9E8C-E518998604C4@mac.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] float.h
Topicbox-Message-UUID: fbf17426-ead3-11e9-9d60-3106f5b1d025

>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.

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

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).