Most negative double value

[Peter Ammon]

What's the most negative double value I can get? Is it always
guaranteed to be -DBL_MAX? If so, why (or rather, where)?

Thanks.

[Malcolm]

"Peter Ammon" <pe*********@ro cketmail.com> wrote in message

What's the most negative double value I can get? Is it always
guaranteed to be -DBL_MAX? If so, why (or rather, where)?

Most floating point formats have a negative flag bit which can be set or
unset. The most natural system is for the maximum and minimum to be of the
same magnitude.

[Papadopoulos Giannis]

Peter Ammon wrote:

What's the most negative double value I can get? Is it always
guaranteed to be -DBL_MAX? If so, why (or rather, where)?

Thanks.

It is DBL_MIN and it is always -DBL_MAX in IEEE-754 compliant systems..

--
#include <stdio.h>
#define p(s) printf(#s" endian")
int main(void){int v=1;*(char*)&v? p(Little):p(Big );return 0;}

Giannis Papadopoulos
http://dop.users.uth.gr/
University of Thessaly
Computer & Communications Engineering dept.

[Peter Ammon]

Papadopoulos Giannis wrote:

Peter Ammon wrote:

What's the most negative double value I can get? Is it always
guaranteed to be -DBL_MAX? If so, why (or rather, where)?

Thanks.

It is DBL_MIN and it is always -DBL_MAX in IEEE-754 compliant systems..

DBL_MIN on my platform is 2.2250738585072 014e-308 which is positive.

--
Pull out a splinter to reply.

[Papadopoulos Giannis]

Peter Ammon wrote:

Papadopoulos Giannis wrote:

Peter Ammon wrote:

What's the most negative double value I can get? Is it always
guaranteed to be -DBL_MAX? If so, why (or rather, where)?

Thanks.

It is DBL_MIN and it is always -DBL_MAX in IEEE-754 compliant systems..

DBL_MIN on my platform is 2.2250738585072 014e-308 which is positive.

F**K.....
I should never post again after 02:00 in the morning...

Yes, the most negative value is -DBL_MAX...
The smallest positive is DBL_MIN...

A big sorry...

--
#include <stdio.h>
#define p(s) printf(#s" endian")
int main(void){int v=1;*(char*)&v? p(Little):p(Big );return 0;}

Giannis Papadopoulos
http://dop.users.uth.gr/
University of Thessaly
Computer & Communications Engineering dept.

[Christian Bau]

In article <c1**********@u lysses.noc.ntua .gr>,
Papadopoulos Giannis <ip******@inf.u th.gr> wrote:

#include <stdio.h>
#define p(s) printf(#s" endian")
int main(void){int v=1;*(char*)&v? p(Little):p(Big );return 0;}

You are aware that this is nonsense?

If not, then think about it for five minutes before you respond.

[CBFalconer]

Peter Ammon wrote:

Papadopoulos Giannis wrote:

Peter Ammon wrote:

What's the most negative double value I can get? Is it always
guaranteed to be -DBL_MAX? If so, why (or rather, where)?

It is DBL_MIN and it is always -DBL_MAX in IEEE-754 compliant systems..

DBL_MIN on my platform is 2.2250738585072 014e-308 which is positive.

Which is apparently correct. From N869:

[#10] The values given in the following list shall be
replaced by implementation-defined constant expressions with
(positive) values that are less than or equal to those
shown:

-- the difference between 1 and the least value greater
than 1 that is representable in the given floating
point type, b1-p

FLT_EPSILON 1E-5
DBL_EPSILON 1E-9
LDBL_EPSILON 1E-9

-- minimum normalized positive floating-point number,
bemin-1

FLT_MIN 1E-37
DBL_MIN 1E-37
LDBL_MIN 1E-37

--
Chuck F (cb********@yah oo.com) (cb********@wor ldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home .att.net> USE worldnet address!

[Dan Pop]

In <c1**********@n ews.apple.com> Peter Ammon <pe*********@ro cketmail.com> writes:

What's the most negative double value I can get? Is it always
guaranteed to be -DBL_MAX?
Yes.
If so, why (or rather, where)?

Because the standard uses a sign-magnitude model for the floating point
numbers. 5.2.4.2.2 in C99. Sorry, but the text is next to impossible
to quote in plain text format, without using some special convention,
a la TeX and friends.

Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Da*****@ifh.de

[Papadopoulos Giannis]

Christian Bau wrote:

In article <c1**********@u lysses.noc.ntua .gr>,
Papadopoulos Giannis <ip******@inf.u th.gr> wrote:

#include <stdio.h>
#define p(s) printf(#s" endian")
int main(void){int v=1;*(char*)&v? p(Little):p(Big );return 0;}

You are aware that this is nonsense?

If not, then think about it for five minutes before you respond.

Please explain...

--
#include <stdio.h>
#define p(s) printf(#s" endian")
int main(void){int v=1;*(char*)&v? p(Little):p(Big );return 0;}

Giannis Papadopoulos
http://dop.users.uth.gr/
University of Thessaly
Computer & Communications Engineering dept.

[Christian Bau]

In article <c1**********@u lysses.noc.ntua .gr>,
Papadopoulos Giannis <ip******@inf.u th.gr> wrote:

Christian Bau wrote:

In article <c1**********@u lysses.noc.ntua .gr>,
Papadopoulos Giannis <ip******@inf.u th.gr> wrote:

#include <stdio.h>
#define p(s) printf(#s" endian")
int main(void){int v=1;*(char*)&v? p(Little):p(Big );return 0;}

You are aware that this is nonsense?

If not, then think about it for five minutes before you respond.

Please explain...

Do you think that bigendian and littleendian are the only possibilities?
Could the char that you are reading consist completely of padding bits
in the int, in which case you could get two different results when you
run the program twice?