<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Understanding Big and Little Endian Byte Order</title>
	<link>http://betterexplained.com/articles/understanding-big-and-little-endian-byte-order/</link>
	<description>Learning shouldn't hurt. Let's share the insights that made difficult ideas click.</description>
	<pubDate>Fri,  5 Dec 2008 08:25:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: dada</title>
		<link>http://betterexplained.com/articles/understanding-big-and-little-endian-byte-order/#comment-216061</link>
		<pubDate>Wed, 26 Nov 2008 12:07:32 +0000</pubDate>
		<guid>http://betterexplained.com/articles/understanding-big-and-little-endian-byte-order/#comment-216061</guid>
					<description>awesome is the word...plesae try to include the solution to the problem in detailed!
thanks,.</description>
		<content:encoded><![CDATA[<p>awesome is the word&#8230;plesae try to include the solution to the problem in detailed!<br />
thanks,.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Kalid</title>
		<link>http://betterexplained.com/articles/understanding-big-and-little-endian-byte-order/#comment-214491</link>
		<pubDate>Fri, 14 Nov 2008 01:49:24 +0000</pubDate>
		<guid>http://betterexplained.com/articles/understanding-big-and-little-endian-byte-order/#comment-214491</guid>
					<description>Hi Shanx, good question. The &quot;magic number&quot; is a special header everyone agrees to write before the data.

If you're reading data and the magic number appears backwards (0xFEFF instead of 0xFFFE), you know the data was stored in a different format and therefore you must byte-swap the data.

This is the strategy used in some Unicode documents -- include a header field so people can tell when someone else wrote it differently. So, you just need to check whether the header == 0xFFFE (same byte order) or header == 0xFEFF (different byte order).</description>
		<content:encoded><![CDATA[<p>Hi Shanx, good question. The &#8220;magic number&#8221; is a special header everyone agrees to write before the data.</p>
<p>If you&#8217;re reading data and the magic number appears backwards (0xFEFF instead of 0xFFFE), you know the data was stored in a different format and therefore you must byte-swap the data.</p>
<p>This is the strategy used in some Unicode documents &#8212; include a header field so people can tell when someone else wrote it differently. So, you just need to check whether the header == 0xFFFE (same byte order) or header == 0xFEFF (different byte order).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Shanx</title>
		<link>http://betterexplained.com/articles/understanding-big-and-little-endian-byte-order/#comment-214447</link>
		<pubDate>Thu, 13 Nov 2008 19:22:55 +0000</pubDate>
		<guid>http://betterexplained.com/articles/understanding-big-and-little-endian-byte-order/#comment-214447</guid>
					<description>Kalid, hi man!

U can explain the thing about put a magic number before every data? I don get it very well =\

If i have a vector of pixels that i pick n my machine is little endian e.g., n the format of pixels is RGBA (bing endian), like this

0 X RR GG BB AA

what is the idea? How i put a magic number before this pixel n mak a test?

Thanks! ^^</description>
		<content:encoded><![CDATA[<p>Kalid, hi man!</p>
<p>U can explain the thing about put a magic number before every data? I don get it very well =\</p>
<p>If i have a vector of pixels that i pick n my machine is little endian e.g., n the format of pixels is RGBA (bing endian), like this</p>
<p>0 X RR GG BB AA</p>
<p>what is the idea? How i put a magic number before this pixel n mak a test?</p>
<p>Thanks! ^^
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
