Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Ian Collins Newsgroups: comp.programming Subject: Re: little-endian Date: Sun, 18 Nov 2012 09:28:16 +1300 Lines: 23 Message-ID: References: <2f491c75-8fbc-4dca-9abe-f11e784454a2@googlegroups.com> <87r4ntp4b1.fsf@informatimago.com> <87mwygpolg.fsf@informatimago.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net inGloGxEij6kGqkrLXSlKwJJpr0w7QC2/0uf/oqd4egmqql2gjvXOQLWwlGSpccloH Cancel-Lock: sha1:Vfc4aij1jR5RBuDbwXMr8eOOfz8= User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:12.0) Gecko/20120423 Thunderbird/12.0 In-Reply-To: Xref: csiph.com comp.programming:2498 On 11/18/12 06:30, BGB wrote: > > typically, a person may develop and use functions like: > ReadInt32BE > and WriteInt64LE and similar, and use these for most of the encoding. Typically a programmer will use the utilities their platform provides. > also, a big downside of using htonl and ntohl as a general mechanism is > that it makes all of ones' libraries need to depend on winsock. That's silly on at least three counts: 1) the whole would doesn't revolve around windows. 2) those utility functions are usually implemented in-line (typically as macros), so there isn't a library dependency. 3) if you are sending data over IP, you need the socket libraries one way or another! -- Ian Collins