FreeTDS Development Group

["Sam Sam" <s4m AT lycos.com>]

--

On Wed, 11 Jul 2001 17:29:39  
 Bob Kline wrote:
>On Wed, 11 Jul 2001, Sam Sam wrote:
>
>> hmmm...
>> ok.. I got a little bit clearer.. 
>> is 11 in intel 0x01010000 ??
>> is 11 in sun   0x00000101 ??
>> if that right I think I got an explanation by that.. =))
>
>No.  This is wandering off topic for this mailing list, but decimal 11
>is stored on an Intel machine as 0B 00 00 00 (assuming we're talking
>about a 32-bit value) and on a SPARC as 00 00 00 0B.

sorry, if it's kinda out of topics... but I mean 11 hexadecimal not 11 
decimal..


Get 250 color business cards for FREE!
http://businesscards.lycos.com/vp/fastpath/

From s4m AT mailcity.com Wed Jul 11 20:51:22 2001
Return-Path: <s4m AT mailcity.com>
Received: from mailcity.com ([209.185.123.188]) by franklin.oit.unc.edu with 
SMTP (Lyris List Manager SOLARIS/SPARC version 4.0); Wed, 11 Jul 2001 
20:51:18 -0400
Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Wed Jul 11 17:50:44 
2001
To: "TDS Development Group" <freetds AT franklin.oit.unc.edu>
Date: Wed, 11 Jul 2001 17:50:44 -0700
From: "Sam Sam" <s4m AT lycos.com>
Message-ID: <MIPCJDNLNCCOBAAA AT mailcity.com>
Mime-Version: 1.0
X-Sent-Mail: off
Reply-To: s4m AT mailcity.com
X-Mailer: MailCity Service
Subject: Re: BIGENDIAN
X-Sender-Ip: 202.155.89.122
Organization: Lycos Mail  (http://mail.lycos.com:80)
Content-Type: text/plain; charset=us-ascii
Content-Language: en
Content-Length: 1121
Content-Transfer-Encoding: 7bit


 
--

On Wed, 11 Jul 2001 13:49:47  
 Michael Peppler wrote:
>Bob Kline writes:
> > On Wed, 11 Jul 2001, Sam Sam wrote:
> > 
> > > isn't 0x01000000 means 2^6=64 while 0x00000001 means 2^0=1 ?? CMIIW
> > > please... why intel use 0x01000000 as representation of 1 ??
> > 
> > It doesn't.  The notation 0xHHHHHHHH (where H is a hex digit) is
> > properly used to represent the logical value of the storage unit.  When
> > the ordering of the bytes used to store that value is to be represented
> > a notation like "HH HH HH HH" is used.  So you might write "an Intel
> > machine stores the value 0x00000001 as 01 00 00 00."  You would not want
> > to write "an Intel machine stores the value 0x00000001 as 0x01000000."
>
>Indeed - my bad, didn't take enough time to properly frame the
>explanation.

I got a little bit clearer.. I think Bob means the big endian and little 
endian used to addressing in memories not a value in memory.. I think it's 
just logical addressing difference.. right guys ??

cheers,
Sam



Get 250 color business cards for FREE!
http://businesscards.lycos.com/vp/fastpath/