Yes. That was a bug (albeit without consequences). So there is undefined behavior... from the programmer
But also from the compiler, because I never got a warning (or used the wrong options).
I guess there are more bugs in the code.
There is a nasty a with TT-hashtables and repetition. But this has little to do with the programming language, because it also happens in the Java version of a OliThink.
Of course, Java is quite strict on those undefined behaviors. Uninitialized variables are not allowed, you don't have access to free pointers and access to arrays is being checked with IndexOutOfBoundExcpetions thrown.