X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=i/r6WtS4C/kPZbKQmhOCfWI955vVMKq8jX7km0GZ9rQ=; b=ZxZsxL8uGrwydE0MSbpopGsjsDFqK6qpxRRO47qu/h3KmXRLXca1lG+yrEuUpvrsjF rJObKAPSwfFwt9gDzf6ie5XLHp3zLy3g7R3Qy3SKuRRQf/cVOQv2zFI/1BGnOMGsGIp4 2h7GAp+104WW1oDmf1cTWATSBXGyKJbIcapF4LJrsveP7g6fkFZYmn7U4qEvQCR7ZJ6S j/dMdx6AmbaQI7SkIYXN8QdV0mDkFCmDEoRjcHf+2WPkSVLed5mLMcXtPBWx+DVIM4La gUrLwljafPRf167bKD7pxUhlOUPdNiif7ATBfYJ7FiXMyWR+E/3Zg3yffgTXg4ekGukq TqRQ== MIME-Version: 1.0 X-Received: by 10.28.3.133 with SMTP id 127mr6714548wmd.101.1452030922069; Tue, 05 Jan 2016 13:55:22 -0800 (PST) In-Reply-To: <20160105090732.GA17930@visitor2.iram.es> References: <201601041946 DOT u04Jkn25014629 AT envy DOT delorie DOT com> <20160105090732 DOT GA17930 AT visitor2 DOT iram DOT es> Date: Tue, 5 Jan 2016 12:55:21 -0900 Message-ID: Subject: Re: [geda-user] Merging stuff. How to make it happen From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a1145278250242105289d4bf6 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --001a1145278250242105289d4bf6 Content-Type: text/plain; charset=UTF-8 > Please, do no use long doubles for anything. While doubles are more or > less standardized on IEEE-754 (or 854?) representation (there are > variations wrt the bit-level representation of NaN and infinities), > there are at least 4 different flavours of long doubles I know of: > float.h in theory characterizes how long doubles behave, though I agree that we don't need them. What would be at least theoretically beneficial would be a float type which can count by ones up the largest integer coordinate you intend to support, e.g. pow (FLT_RADIX, DBL_MANT_DIG) > COORD_MAX. There are some more details in another thread I just cc'd. Britton --001a1145278250242105289d4bf6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=
Please, do no use long doubles for anything. While doubles= are more or
less standardized on IEEE-754 (or 854?) representation (there are
variations wrt the bit-level representation of NaN and infinities),
there are at least 4 different flavours of long doubles I know of:

float.h in theory characterizes how = long doubles behave, though I agree that we don't need them.

What would be at least theoretically b= eneficial would be a float type which can count by ones up the largest inte= ger coordinate you intend to support, e.g.=C2=A0pow (FLT_RADIX, DBL_MANT_DI= G) > COORD_MAX.=C2=A0 There are some more details in another thread I ju= st cc'd.

Britton
--001a1145278250242105289d4bf6--