From: Endlisnis <s257m AT unb DOT ca>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: pointers and errors make cephaler go crazy
Date: Thu, 13 Aug 1998 00:02:36 -0300
Organization: NBTel Internet
Lines: 32
Message-ID: <35D2574C.C3A13863@unb.ca>
References: <01bdc535$858a16c0$0100007f AT scully> <35D0BA17 DOT 21A5DC36 AT unb DOT ca> <01bdc5f1$d169bd40$78c3b8cd AT scully>
NNTP-Posting-Host: fctnts10c24.nbnet.nb.ca
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Cephaler wrote:

> Endlisnis <s257m AT unb DOT ca> wrote in article <35D0BA17 DOT 21A5DC36 AT unb DOT ca>...
> > Why not just make it:_tile map[100][100];
> Well I did that before, and it worked for a while, then it didn't (SIGILL
> ahhh!!!) so I rewrote all my code using pointers, and now I try to
> recompile and something is wrong with my file io code aaaaaaaaaaargh sigh
> I'll never finish this
> > What was the error that the compiler gave you on this line of code
> (without the
> > '&').  And what is 'blit' & 'tiles'.
> Blit = allegro function, tiles = array of 256 allegro BITMAPs... Don't
> think there was an error, just at runtime it gave me strange values

    But, using array's instead of pointers shouldn't produce SIGILL.  Isn't
that trying to execute a command which doesn't exist?  That should not be
cause by using arrays, that (AFAIK) could only be cause by jumping into data
(or uninitialized memory).  Some things that could cause SIGILL would be
screwing around with the stack in a function, ... using an uninitialized or
wrong function pointer, stuff like that.  It shouldn't be generated by using
arrays (unless you are trying to optimize for Pentium when you are running a
486 or something like that).

--
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT GeoCities DOT com
          Endlis AT nbnet DOT nb DOT ca