• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
formalproof

Why does a byte array <-> integer type cast "reverse" order of bytes?

5 posts in this topic

I'm working on a project where I need to convert the bit pattern in an integer type to an array of chars (bytes), and vice versa. I'm wondering why this conversion always seems to "reverse" the order of the bytes. For example, when converting val = 0xAABBCCDD to an array of chars, the first element of the array will be 0xDD, the second 0xCC, etc., although I'm using a little endian system.

For me, the logical order would be 0xAA, 0xBB, 0xCC, 0xDD, because that is the order in which the bytes of val are stored in memory, isn't it?

Here is the code:
[code]
#include <iostream>
#include <vector>
using namespace std;
int main()
{
int one = 0x1;
cout << "The system is " << (((one << 1) == 0)? "big endian" : "little endian") << endl;
// This will output "little endian" on my system
vector<char> vec;
vec.push_back(0xAA);
vec.push_back(0xBB);
vec.push_back(0xCC);
vec.push_back(0xDD);
unsigned long* ul = reinterpret_cast<unsigned long*>(&vec[0]);
cout << hex << *ul << endl; // Why does this output 0xDDCCBBAA?

unsigned long n = 0xAABBCCDD;
vector<char> w;
w.assign( reinterpret_cast<char*>(&n), reinterpret_cast<char*>(&n) + sizeof(unsigned long) );
for(int i = 0; i < w.size(); i++) {
cout << hex << (int)(unsigned char)w[i]; // this cast is because we want to print the bit pattern of w[i], not the character
}
cout << endl; // This will output in the "reverse" order as well: 0xDDCCBBAA0000
}
[/code]

So I'm asking whether someone can explain to me why the order of bytes after conversion is 0xDDCCBBAA and not 0xAABBCCDD?

Btw, if you know a better way to convert between an integer type and a vector of chars, or notice any other stupidities in my code, please let me know. :)
0

Share this post


Link to post
Share on other sites
[quote name='ApochPiQ' timestamp='1341960734' post='4957812']
The technical term for this is "[url="http://en.wikipedia.org/wiki/Endianness"]endianness[/url]".
[/quote]

Ok, seems I made an embarassing mistake in understanding what little endian means [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]

So in a little endian system, val = 0xAABBCCDD is stored in memory as:
0 1 2 4
DD CC BB AA

That would explain why vec[0] == 0xDD, etc. Thanks! Edited by formalproof
0

Share this post


Link to post
Share on other sites
Just a note: your test for endianness is wrong. [font=courier new,courier,monospace](one << 1)[/font] will always equal 2, regardless of little endian or big endian. There are a couple of reasons for this. First, a single byte has no endianness (endianness has nothing to do with how the [i]bits [/i]are stored in the [i]bytes[/i]; it is all about how the [i]bytes [/i]are arranged to make[i] bigger data types[/i]). It looks like in that test you're expecting the bits to be big/little endian, which is the wrong way to think about it.

Second, operator << is defined such that 1 << 1 is always 2, regardless of endianness (and 1 << 8 is always 256, and 1 << 9 is always 512, etc). It doesn't care about endianness. The compiler is responsible for making sure this holds true, whatever the endianness is.

You don't want to check what the [i]value [/i]of something is in order to find out if it's big or little endian. You want to check how the [i]bytes [/i]are [i]ordered [/i]to find out its endianness.

Endianness is known at compile time (the compiler has to know in order to create the right machine code), so normally people will just check for the appropriate compiler macro flag to see if it's big or little endian. I know of some ways to find out if a computer is big or little endian at run time with code, but these ways that I know make certain assumptions and aren't truly cross platform checks anyway (I don't know of any truly cross platform way to check for endianness). Edited by Cornstalks
0

Share this post


Link to post
Share on other sites
I wouldn't even check compiler macros, just use functions like htobe16, le64toh etc. I don't know, if they are available in Microsoft compilers though. At least for up to 32 bits, ntohs, ntohl, htons and htonl should be supported everywhere.
1

Share this post


Link to post
Share on other sites
You should never need to check endianess for a compiler or CPU architecture (unless you are in the business of making compilers). When you see someone doing that, they have usually misunderstood something.

You do care about byte order in protocol and binary files, but that should be independent of the current architecture. Please see [url="http://commandcenter.blogspot.com/2012/04/byte-order-fallacy.html"]The byte order fallacy[/url] for a more detailed explanation.
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0