From:	Endlisnis <s257m AT unb DOT ca>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: ? array[n] or array[n+1] ?
Date:	Sat, 15 May 1999 00:47:23 -0400
Organization:	BrunNet
Lines:	26
Message-ID:	<373CFC5B.3E5297D4@unb.ca>
References:	<37367f71 DOT 6271443 AT news DOT wanadoo DOT fr> <3736A098 DOT 55E268BE AT softhome DOT net> <373c0195 DOT 3902906 AT news DOT wanadoo DOT fr> <3737f542 DOT 0 AT nnrp1 DOT news DOT uk DOT psi DOT net> <3739F455 DOT 1818FDD7 AT unb DOT ca> <373a1915 DOT 3102234 AT noticias DOT iies DOT es> <373B61C6 DOT 20FA8B62 AT unb DOT ca> <373d718b DOT 2239096 AT noticias DOT iies DOT es>
NNTP-Posting-Host:	ftnts2c9.brunnet.net
Mime-Version:	1.0
X-Mailer:	Mozilla 4.51 [en] (Win95; U)
X-Accept-Language:	en
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Guillermo Rodriguez Garcia wrote:

> >> >Outcome #3:  Something terrible might happen.  Worst case scenario (never known
> >> >anyone it has happened to, but it's possible): overwriting some buffered portion
> >> >of a hard-drive or memory mapped io could desroy data or hardware.
> >> Hardware? You must be joking.
> >    Well, there's the old story about the non-multi-sync monitors that you could
> >break if you switched the mode too fast.
> OK, I get the idea. But I think it is just too difficult to make any
> of these things happen.

    You can usually just ignore it, and most of the time screwing with memory will do
nothing or make your program crash.  I've talked to many programmers and I've never
actually hear of a recent even of hardware breakage, so you can put it out of your mind
unless you are working on an old machine or on a VERY CRITICAL system.  All-in-all, it
is practically impossible to accidentally hurt hardware, but my point was to show you
that it was still possible under certain very unlikely conditions.  (odds around 1 in
2^10000)
--
     (\/) Endlisnis (\/)
          s257m AT unb DOT ca
          Endlisnis AT HotMail DOT com
          ICQ: 32959047

- Raw text -