Thread: why i get this run time error..

C is like a loving parent. It likes you to learn from your mistakes. It's not going to stop you from wandering off the path into the tiger infested jungle. It knows that you'll eventually learn from your mistakes.

Even if that means you get mauled by a tiger.

C loves you.


Quzah.

Why should it? Undefined behavior is just that, undefined. Anything can happen. That's why we get posts like "This code worked for me!" when they're copying stuff into pointers which haven't been assigned any value, etc. It MIGHT let you access that memory, it might not:

Code:

int *x;
*x = 10;

Maybe it crashes, maybe it doesn't. Maybe it does for you, but not for me? Who knows. It's not defined.


Quzah.

Originally Posted by transgalactic2

but i should get an error on some operation on the array
why it goes on the last line of the function

Because to keep some resemblance of performance, the compiler only checks that you haven't wandered off into the weeds when the function returns, rather than every single memory access.

--
Mats

Originally Posted by transgalactic2

on codeblocks compiler it works fine
but on VS it gives me that run time error
??

No, in Code::Blocks, the error goes undetected - that is not the same as "works fine". That is, as quzah describes, one of the probems with undefined behaviour. Writing outside an array [which I'm fairly sure is what you are doing - posting your code would help a lot] is undefined behaviour, it may cause ANYTHING to happen, and "anything" includes "nothing that you actually notice" as well as crashes, nuclear launch and explosion of the hard-disk.

--
Mats