From: ori@eigenstate.org
To: 9fans@9fans.net
Subject: Re: [9fans] ntohl, htonl, &c
Date: Fri, 13 May 2022 18:37:33 -0400 [thread overview]
Message-ID: <8CB6493171ADDFFD03A47AB46EE6B568@eigenstate.org> (raw)
In-Reply-To: <948B711D-CD62-4467-BDA1-7370873E26BF@quintile.net>
Quoth Steve Simon <steve@quintile.net>:
> ntohl in libc?
> say its not so?
definitely not the byte swapping versions.
the unpacking of known bytes with known endianness
into an integer, though, is a sensible API that
many programs copy and paste; it's trivial to write,
but it's also common.
I don't feel strongly that it needs to be there, but
I dont' object to it either.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tbf58310b561cd180-M67c8b4f012da468975a17d1e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-05-13 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 11:50 adr
2022-05-13 13:11 ` Alex Musolino
2022-05-13 14:22 ` ori
2022-05-13 15:51 ` adr
2022-05-13 16:42 ` adr
2022-05-13 21:23 ` ori
2022-05-13 22:29 ` Steve Simon
2022-05-13 22:37 ` ori [this message]
2022-05-14 10:45 ` adr
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=8CB6493171ADDFFD03A47AB46EE6B568@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).