Mail Archives: djgpp-workers/2003/09/13/16:06:27
--part1_20.18ae4e3c.2c94d286_boundary
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Rich Dawe:
Judging from the text that I see in the Posix Standard for math.h, much work=
=20
lies ahead to implement DJGPP 2.04. For example:
> The following macro shall expand to an expression that has type int and th=
e=20
> value MATH_ERRNO, MATH_ERREXCEPT, or the bitwise-inclusive OR of both:
>=20
>=20
> >> math_errhandling
>>=20
>=20
> The value of math_errhandling is constant for the duration of the program.=
=20
> It is unspecified whether math_errhandling is a macro or an identifier wit=
h=20
> external linkage. If a macro definition is suppressed or a program defines=
an=20
> identifier with the name math_errhandling , the behavior is undefined. If=20=
the=20
> expression (math_errhandling & MATH_ERREXCEPT) can be non-zero, the=20
> implementation shall define the macros FE_DIVBYZERO, FE_INVALID, and FE_OV=
ERFLOW in <A HREF=3D"http://www.opengroup.org/onlinepubs/007904975/basedefs/=
fenv.h.html">.
This text was copied from the Posix Standard at the following URL:
<A HREF=3D"http://www.opengroup.org/onlinepubs/007904975/toc.htm">ht=
tp://www.opengroup.org/onlinepubs/007904975/toc.htm</A>
The documents are entitled:
The Open Group Base Specifications Issue 6
IEEE Std 1003.1, 2003 Edition
Copyright =A9 2001-2003 The IEEE and The Open Group, All Rights reserved
The same text is contained in a document with the name "xshtext.pdf" that I=20
obtained by using directions from Eli Zaretskii. I am no longer able to fin=
d=20
the document; that reveals how browser-challenged I am when it comes to find=
ing=20
anything that is unfamiliar on the Web.
I've been using these documents as a basis for some of my documentation.
I discovered this new requirement (new to me, anyway) when I began to review=
=20
my documentation for hypotl.c. Apparently, the hypot() functions are suppos=
ed=20
to do something with macro "math_errhandling" when the possibility of either=
=20
overflow or underflow is detected. That means that the program needs to be=20
modified, not to mention the documentation.
KB Williams
--part1_20.18ae4e3c.2c94d286_boundary
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><FONT FACE=3Darial,helvetica><FONT SIZE=3D3 FAMILY=3D"SERIF" FACE=3D"=
Georgia" LANG=3D"0">Rich Dawe:<BR>
<BR>
Judging from the text that I see in the Posix Standard for math.h, much work=
lies ahead to implement DJGPP 2.04. For example:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">The following macro shall expan=
d to an expression that has type <B>int</B> and the value MATH_ERRNO, MATH_E=
RREXCEPT, or the bitwise-inclusive OR of both:<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">math_errhandling<BR>
</BLOCKQUOTE><BR>
<BR>
The value of math_errhandling is constant for the duration of the program. I=
t is unspecified whether math_errhandling is a macro or an identifier with e=
xternal linkage. If a macro definition is suppressed or a program defines an=
identifier with the name math_errhandling , the behavior is undefined. If t=
he expression (math_errhandling & MATH_ERREXCEPT) can be non-zero, the i=
mplementation shall define the macros FE_DIVBYZERO, FE_INVALID, and FE_OVERF=
LOW in <I><A HREF=3D"http://www.opengroup.org/onlinepubs/007904975/basedefs/=
fenv.h.html"><fenv.h></A></I></I>.</BLOCKQUOTE><BR>
<BR>
This text was copied from the Posix Standard at the following URL:<BR>
<BR>
<A HREF=3D"http://www.opengroup.org/on=
linepubs/007904975/toc.htm">http://www.opengroup.org/onlinepubs/007904975/to=
c.htm</A><BR>
<BR>
The documents are entitled:<BR>
</FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2=
FAMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0"><BR>
<P ALIGN=3DCENTER>The Open Group Base Specifications Issue 6<BR>
IEEE Std 1003.1, 2003 Edition<BR>
Copyright =A9 2001-2003 The IEEE and The Open Group, All Rights reserved<BR>
<P ALIGN=3DLEFT></FONT><FONT COLOR=3D"#000000" style=3D"BACKGROUND-COLOR: #=
ffffff" SIZE=3D3 FAMILY=3D"SERIF" FACE=3D"Georgia" LANG=3D"0"><BR>
<BR>
The same text is contained in a document with the name "xshtext.pdf" that I=20=
obtained by using directions from Eli Zaretskii. I am no longer able t=
o find the document; that reveals how browser-challenged I am when it comes=20=
to finding anything that is unfamiliar on the Web.<BR>
<BR>
I've been using these documents as a basis for some of my documentation.<BR>
<BR>
I discovered this new requirement (new to me, anyway) when I began to review=
my documentation for hypotl.c. Apparently, the hypot() functions are=20=
supposed to do something with macro "math_errhandling" when the possibility=20=
of either overflow or underflow is detected. That means that the progr=
am needs to be modified, not to mention the documentation.<BR>
<BR>
<BR>
<BR>
KB Williams</P></P></FONT></HTML>
--part1_20.18ae4e3c.2c94d286_boundary--
- Raw text -