linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: r_zaca <r_zaca@ig.com.br>
To: linux-c-programming@vger.kernel.org
Subject: Re: Byte Order
Date: Thu, 13 Jan 2005 08:05:57 -0200	[thread overview]
Message-ID: <20050113_100557_072441.r_zaca@ig.com.br> (raw)

[-- Attachment #1: Mail message body --]
[-- Type: text/plain, Size: 1746 bytes --]

  Thanks a lot, that is what I was looking for. A simple test that I can do, 
using some C conde, to find out if the machine where the program is running 
on uses Big or Little endian "memory organization". 


On Wed, 2005-01-12 15:03:57 -0200, r_zaca <r_zaca@ig.com.br> 
wrote in message <20050112_170357_014648.r_zaca@ig.com.br>: 
Content-Description: Mail message body 
>   How can I say if the machine where I am working uses "Host Byte 
Order" or 
> "Network Byte Order"? 

Something like this should do the job: 

#include <stdint.h> 
#include <stdio.h> 
#include <stdlib.h> 

int 
main (int argc, char *argv[]) 
{ 
        uint32_t i = 0x44332211; 
        unsigned char *c; 

        c = (unsigned char *) &i; 

        if (c[0] == 0x11 && c[1] == 0x22 && c[2] == 0x33 && c[3] == 0x44) 
                printf ("This is a little-endian host\n"); 
        else if (c[0] == 0x44 && c[1] == 0x33 && c[2] == 0x22 && c[3] == 
0x11) 
                printf ("This is a big-endian host\n"); 
        else if (c[0] == 0x33 && c[1] == 0x44 && c[2] == 0x11 && c[3] == 
0x22) 
                printf ("This is a pdp-endian host\n"); 
        else { 
                printf ("This host is broken:-)\n"); 
                return EXIT_FAILURE; 
        } 

        return EXIT_SUCCESS; 
} 


>   Is it an obvius question? I mean, all hosts (machines) uses "Host 
Byte 
> Order" and when it needs to send data through the network it uses 
"Network 
> Byte Order". 

The rule is easy: Just *always* either use htonl/htons/ntohl/ntohs or 
transmit the number in readable format. The nice thing is that any sane 
libc will implement those as macros, so if your host already works in 
network byte order, the conversion will get optimized away. 

MfG, JBG 

             reply	other threads:[~2005-01-13 10:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 10:05 r_zaca [this message]
2005-01-14 21:31 ` Byte Order Glynn Clements
  -- strict thread matches above, loose matches on Subject: below --
2005-01-12 17:03 r_zaca
2005-01-12 17:31 ` Eric Bambach
2005-01-12 17:34 ` Jan-Benedict Glaw

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=20050113_100557_072441.r_zaca@ig.com.br \
    --to=r_zaca@ig.com.br \
    --cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).