<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Short Size in ColdFire/68K Microcontrollers and Processors</title>
    <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Short-Size/m-p/195089#M8614</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BR /&gt;The purpose of uint32, uint16 etc. is that they are adjusted for the environment you are in so that they are always that size regardless.&lt;BR /&gt;&lt;BR /&gt;So if you use uint32, and you change compilers, processor, or compile options these are adjustedt in one place, vs all over if you use unsigned int.&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 18 Oct 2008 03:25:45 GMT</pubDate>
    <dc:creator>JimDon</dc:creator>
    <dc:date>2008-10-18T03:25:45Z</dc:date>
    <item>
      <title>Short Size</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Short-Size/m-p/195087#M8612</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello there,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Using the compiler option 4-byte integer, a short will have, always, 2 bytes?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I can't understand exactaly the definitions of uint32, uint16... and how the compiler handles them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Oct 2008 01:05:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Short-Size/m-p/195087#M8612</guid>
      <dc:creator>carlosmscabral</dc:creator>
      <dc:date>2008-10-18T01:05:22Z</dc:date>
    </item>
    <item>
      <title>Re: Short Size</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Short-Size/m-p/195088#M8613</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;&amp;gt; Using the compiler option 4-byte integer, a short will have, always, 2 bytes?&lt;BR /&gt;No, this is an architecture dependent.&lt;/DIV&gt;&lt;DIV&gt;But, sizeof(short int) is 2 bytes for&amp;nbsp;all known to me&amp;nbsp;32-bit architectures.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;gt; I can't understand exactly the definitions of uint32, uint16... and how the compiler handles them.&lt;BR /&gt;Regularly, UINT32 has the range from 0 to 2^31-1.&lt;/DIV&gt;&lt;DIV&gt;Regularly, UINT16 has the range from 0 to 2^15-1.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Oct 2008 01:38:05 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Short-Size/m-p/195088#M8613</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2008-10-18T01:38:05Z</dc:date>
    </item>
    <item>
      <title>Re: Short Size</title>
      <link>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Short-Size/m-p/195089#M8614</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BR /&gt;The purpose of uint32, uint16 etc. is that they are adjusted for the environment you are in so that they are always that size regardless.&lt;BR /&gt;&lt;BR /&gt;So if you use uint32, and you change compilers, processor, or compile options these are adjustedt in one place, vs all over if you use unsigned int.&lt;BR /&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 18 Oct 2008 03:25:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/ColdFire-68K-Microcontrollers/Short-Size/m-p/195089#M8614</guid>
      <dc:creator>JimDon</dc:creator>
      <dc:date>2008-10-18T03:25:45Z</dc:date>
    </item>
  </channel>
</rss>

