Hello,
You know when we define an integer it takes an uninitalized random number. The thing is , this number is always the same when I execute the program. Shouldnt it take different varies each time because it is random ?
Hello,
You know when we define an integer it takes an uninitalized random number. The thing is , this number is always the same when I execute the program. Shouldnt it take different varies each time because it is random ?
The value isn't (necessarily) random, just undefined.
Random doesn't mean that you get a different value every single time.
If you change the program and recompile, it might be different.
If you change the compiler options, it might be different.
If you change the compiler, it might be different.
If you change the OS, it might be different.
Random means that you have no way to predict what the value(s) are going to be given the circumstances under which it was compiled and run.
Sure, it may seem like a constant for any given simple program, but you sure can't extrapolate that observation to every program in every circumstance.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Ehm, you mean a local variable inside main (or some other function).
I guess I (and others) are sloppily calling these numbers "random garbage", but it's not random in that sense.
Yes, it will often have the same value each time you run the code. It is only random from a more big-picture perspective - it is UNDEFINED, which means that it can have ANY value. It is not random in the way that it's going to be decidedly different values every time, but if you compile the same program with a different compiler, it's highly likely that it has a different value - even changing the compiler parameters (such as enabling/disabling optimization) or making changes to the code itself could make it change.
If you want real random numbers, then you should use a random number generator.
The point about undefined variable values (and other undefined behaviour) is that it is NOT DEFINED - it can be anything, it's not guaranteed to stay the same, and it may cause problems later on if you expect it to stay this way.
Note also that some compilers have settings where you can "initialize all variables to a defined value", which for example will make all uninitialized local variables have a defined value - this is to help you find the problem of uninitialized variables - sometimes the compielr will even detect these things and tell you explicitly: You are using X when it's uninitialized. In this case, the value is very much DEFINED. However, this also makes the code slower, because each function will have a bunch of code to set all the local variables to some fixed value.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
