Erm, actually, no he's not. It's up to the compiler how to arrange your variables in memory and it could well have put array before ray. Maybe because it arranges them by descending size or because...
Type: Posts; User: QuantumPete
Erm, actually, no he's not. It's up to the compiler how to arrange your variables in memory and it could well have put array before ray. Maybe because it arranges them by descending size or because...
A Very Bad Thing. Probably the only thing that is saving you is the fact that "ray" is a global. Thus it will be stored in the global part of memory, which on many architectures is at the bottom of...
There is your problem. You can't do that. Arrays can't grow dynamically. It's pretty much the definition of an array that it has a set size. Once an array has a certain set of dimensions it can't be...
It looks to me like the variable is called new (how that got by the compiler I don't know), no dynamic allocation.
QuantumPete
My money is still on stack corruption ;)
QuantumPete
Sounds like a classic stack corruption. Can you post your code?
QuantumPete