From: "A. Sinan Unur" Newsgroups: comp.os.msdos.djgpp Subject: Re: Puzzling pointer behaviour Date: 13 Oct 2001 15:07:21 GMT Organization: Cornell University Lines: 25 Sender: asu1 AT cornell DOT invalid (on slip-32-102-40-146.ny.us.prserv.net) Message-ID: References: <9q90ti$8p9$1 AT epos DOT tesco DOT net> NNTP-Posting-Host: slip-32-102-40-146.ny.us.prserv.net X-Trace: news01.cit.cornell.edu 1002985641 17410 32.102.40.146 (13 Oct 2001 15:07:21 GMT) X-Complaints-To: usenet AT news01 DOT cit DOT cornell DOT edu NNTP-Posting-Date: 13 Oct 2001 15:07:21 GMT User-Agent: Xnews/4.06.22 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Graham Warren" wrote in news:9q90ti$8p9$1 AT epos DOT tesco DOT net: > Hello, > Thankyou to all who have helped me in the past. > > I've come across something slightly strange about byte pointers. Can > anyone explain this. This small program demonstrates my query. When a > byte pointer is made to point to an long int pointer, it actually > points to the 8 least significant bits of the long int. Also, when this > byte pointer is incremented it points 'left' of its original position. > Why is this? This is really off-topic here. However, see http://www.tuxedo.org/~esr/jargon/html/entry/little-endian.html and http://developer.gnome.org/doc/API/glib/glib-byte-order-macros.html -- -------------------------------- A. Sinan Unur http://www.unur.com/