public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "majic.one at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/14988] Add ntohd(), ntohf(), ntohll(), htond(), htonf(), htonll() for sending/receiving IEEE 754-formatted floats/doubles/long-longs
Date: Thu, 07 Mar 2013 04:52:00 -0000 [thread overview]
Message-ID: <bug-14988-131-d3E7nMDGm1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14988-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14988
--- Comment #2 from Majic <majic.one at gmail dot com> 2013-03-07 04:52:25 UTC ---
(In reply to comment #1)
> Are these functions purely Microsoft-isms, or are they available on actual
> implementations of the BSD sockets API?
>
> (I'm asking because we're not goint to add CreateFile etc., either. 8-)
As far as I am aware, these are only found on Windows (8) atm. :> I have not
seen them anywhere else. I would also not be interested in a CreateFile(), but
I do feel like Microsoft has met a need here. Using snprintf() with its %a
conversion specifier to go from a double to a hex string and then later
converting it back is unnecessarily costly.. I hope this is not too
presumptuous to say, but glibc (being a major player) could add these and
encourage their acceptance into POSIX. Microsoft didn't exactly do anything
strange extending beyond htons() with these. I know the focus of glibc isn't
to set standards but to adhere to them. I just feel like in 2013 there should
be at least a glibc-standard way of sending network floats (and receiving
them).
Again, I hope I'm not expecting too much :>
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-03-07 4:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 6:20 [Bug network/14988] New: " majic.one at gmail dot com
2012-12-30 6:23 ` [Bug network/14988] " majic.one at gmail dot com
2013-01-14 14:51 ` fweimer at redhat dot com
2013-03-07 4:52 ` majic.one at gmail dot com [this message]
2014-01-16 5:50 ` allan at archlinux dot org
2014-06-14 5:28 ` 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-14988-131-d3E7nMDGm1@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).