Thread: LIT output
View Single Post
Old 12-19-2008, 03:13 PM   #8
=X=
Wizard
=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.=X= ought to be getting tired of karma fortunes by now.
 
=X='s Avatar
 
Posts: 3,671
Karma: 12205348
Join Date: Mar 2008
Device: Galaxy S, Nook w/CM7
Quote:
Originally Posted by llasram View Post
Er, yes. That was what passes for a joke in my tribe.
Ah well yes, it was late I see the sarcasm now .

Quote:
Originally Posted by llasram View Post
That would be one of the two outstanding issues .. .
My aplogoizes I did not mean to rehash known issues.


Quote:
Originally Posted by igorsk View Post
You can detect endianness at runtime. Grabbed from some random page:
Code:
Uint32 Value32;
Uint8 *VPtr = (Uint8 *)&Value32;

VPtr[0] = VPtr[1] = VPtr[2] = 0; VPtr[3] = 1;

if(Value32 == 1)
   printf("I'm big endian\n");
else
   printf("I'm little endian\n");
I use to be in favor of dong these checks in my code, but as systems are transitioning from 32 to 64 bit. It will complicate ones code w/o need. Its best to allow the OS to handle the edian/memory. Just make sure the macros work .

=X=
=X= is offline   Reply With Quote