From: "Joseph S. Myers" <joseph-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
Cc: libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org,
Andreas Jaeger <aj-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org>,
Andries Brouwer <Andries.Brouwer-rh8NL+sEX9E@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Report bugs for variations in error handling in math functions?
Date: Fri, 25 Jul 2008 17:06:17 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.64.0807251701570.7701@digraph.polyomino.org.uk> (raw)
In-Reply-To: <cfd18e0f0807250853q636b8d2dx8cefd53bc672b7a9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, 25 Jul 2008, Michael Kerrisk wrote:
> Not even one approach is consistent. Many functions don't set errno.
> But there are one or two that don't raise exceptions: the Bessel
> functions (j0(), y0 etc), for example. It's all a bit of a mess,
> unfortunately.
Those functions aren't in C99. They are however in POSIX, which defines
C99-like error handling requirements, though a lot of errors are "may
occur" just as a lot of C99 ones are. (But if a "may occur" error is
indicated by one of errno and exceptions, it must be indicated by both if
math_errhandling says both forms of error handling are supported.)
(Bessel functions under different names and a lot of other functions are
in DIS 24747, which passed its ballot for approval as an International
Standard. But I don't expect it to be integrated in the next revision of
the C standard; my understanding is also that all of C++ TR1 *apart* from
special mathematical functions (much the same set) is being integrated in
C++0x.)
--
Joseph S. Myers
joseph-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-07-25 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 10:14 Report bugs for variations in error handling in math functions? Michael Kerrisk
[not found] ` <cfd18e0f0807250314h5c063754gd672c04b2eeef2f6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-25 15:43 ` Joseph S. Myers
[not found] ` <Pine.LNX.4.64.0807251535040.7701-9YEB1lltEqivcGRMvF24k2I39yigxGEX@public.gmane.org>
2008-07-25 15:53 ` Michael Kerrisk
[not found] ` <cfd18e0f0807250853q636b8d2dx8cefd53bc672b7a9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-25 17:06 ` Joseph S. Myers [this message]
2008-07-28 5:54 ` Michael Kerrisk
[not found] ` <cfd18e0f0807272254k54343bc3pdddde9afca423eec-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-07-28 17:05 ` Joseph S. Myers
2008-07-31 14:02 ` Michael Kerrisk
[not found] ` <4891C60A.5000103-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-08-04 5:48 ` Michael Kerrisk
[not found] ` <cfd18e0f0808032248l3f9d7ef4r2af2a989da4d9eb9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-06 9:27 ` Michael Kerrisk
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=Pine.LNX.4.64.0807251701570.7701@digraph.polyomino.org.uk \
--to=joseph-qd8j1lwmmjjtcj0u4l0sbw@public.gmane.org \
--cc=Andries.Brouwer-rh8NL+sEX9E@public.gmane.org \
--cc=aj-Et1tbQHTxzrQT0dZR+AlfA@public.gmane.org \
--cc=libc-alpha-9JcytcrH/bA+uJoB2kUjGw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
/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