public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jaak at ristioja dot ee" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/16459] endian.h does not define byte-order conversion functions
Date: Thu, 16 Jan 2014 19:49:00 -0000 [thread overview]
Message-ID: <bug-16459-131-GaitW6Uc4p@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16459-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16459
--- Comment #2 from Jaak Ristioja <jaak at ristioja dot ee> ---
(In reply to joseph@codesourcery.com from comment #1)
> glibc does not provide manpages, and they are not relevant to what glibc's
> interface should be. (glibc's code should of course be consistent with
> the manual shipped with glibc; I haven't checked what if anything that
> says about these interfaces.)
It appears that these interfaces are undocumented in the Texinfo manual.
Why not just add these as functions also, e.g. as done with htons and friends
in <netinet/in.h>:
extern uint16_t htons (uint16_t __hostshort)
__THROW __attribute__ ((__const__));
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-01-16 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 12:52 [Bug libc/16459] New: " jaak at ristioja dot ee
2014-01-16 19:01 ` [Bug libc/16459] " joseph at codesourcery dot com
2014-01-16 19:49 ` jaak at ristioja dot ee [this message]
2014-01-16 20:50 ` Ondřej Bílka
2014-01-16 20:51 ` neleai at seznam dot cz
2014-06-13 8:55 ` fweimer at redhat dot com
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=bug-16459-131-GaitW6Uc4p@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).