Posted by Peter Hill on December 07, 2001 at 11:07:17:
In Reply to: Re: fixed it posted by William D McQuain on December 04, 2001 at 13:47:03:
: : : : : I had a different error in there that was causing it.
: : : :
: : : : If u use const ref. to pass to a function. u r not able to make any change in the funtion.
: : : : like...assigning this cell to another.
: : : : this would cause error
: : : True, but that would cause a compile-time error, not a run-time error.
: : how about.....using a cell which is out of range?
: That may cause a run-time error, or not.
: It depends on whether your program "owns" that memory location. If it does, then there won't necessarily be a run-time error but there will probably be a logical error since SOMETHING lives at that address and you'll probably mess it up.
: If your program doesn't own that address, then there should be a run-time error, but that depends on what OS you're using. If you're running Windows 95/98/Me there's a good chance that there won't be a run-time error because the OS is essentially too feeble to detect that your program has done something illegal.
: If you're running Windows NT/2000 (and maybe XP) then there will almost certainly be a run-time error.
Just for reference when I use memory that I don't "own" in XP, it does give me a runtime error.
Post a Followup