From: Andreas Ericsson <ae@op5.se>
To: "Ramsay Jones" <ramsay@ramsay1.demon.co.uk>,
"Torsten Bögershausen" <tboegi@web.de>
Cc: "Vicent Martí" <tanoku@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>, git <git@vger.kernel.org>,
"Jeff King" <peff@peff.net>
Subject: Re: htonll, ntohll
Date: Wed, 13 Nov 2013 13:20:20 +0100 [thread overview]
Message-ID: <52836E84.3020901@op5.se> (raw)
In-Reply-To: <52783518.1030908@ramsay1.demon.co.uk>
On 2013-11-05 01:00, Ramsay Jones wrote:
>
> [Note: I have never particularly liked htons, htonl et.al., so adding
> these htonll/ntohll functions doesn't thrill me! :-D For example see
> this post[1], which echo's my sentiments exactly.]
>
That post actually contradicts your statement, as it clearly states
that "someone at Adobe figured out about byte order and there would
have been no problems transferring files between (big-endian and
little-endian) machines... if the people at Adobe wrote proper code
to encode and decode their files".
htonl(), ntohl(), htons(), ntohs() are those "encode" and "decode"
functions. If you or the author of the post you linked think otherwise,
you're misinformed and need to learn what encoding and decoding means.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
prev parent reply other threads:[~2013-11-13 12:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 19:28 What's cooking in git.git (Oct 2013, #07; Mon, 28) Junio C Hamano
2013-10-28 21:58 ` Thomas Rast
2013-10-30 16:51 ` Torsten Bögershausen
2013-10-30 17:01 ` Vicent Martí
2013-10-30 17:14 ` Torsten Bögershausen
2013-10-30 17:39 ` Torsten Bögershausen
2013-10-30 19:11 ` Ramsay Jones
2013-10-30 19:06 ` Ramsay Jones
2013-10-30 20:30 ` Torsten Bögershausen
2013-10-30 21:07 ` Ramsay Jones
2013-10-31 13:24 ` htonll, ntohll Torsten Bögershausen
2013-11-05 0:00 ` Ramsay Jones
2013-11-06 15:58 ` Torsten Bögershausen
2013-11-12 14:44 ` Jakub Narębski
2013-11-13 12:20 ` Andreas Ericsson [this message]
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=52836E84.3020901@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=ramsay@ramsay1.demon.co.uk \
--cc=tanoku@gmail.com \
--cc=tboegi@web.de \
/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).