This is related to Borland 5.02 C++ compiler for an OWL program.
Someone I work with noticed this occurring for large variable:
When x was true and they stepped into routine2() the stack blew up, BUT (Here is the weird part)
if the size of averylargevariable1 was changed to , the program worked fine.
It appears that the space for averylargevariable1 was being allocated even though the curley braces were not currently being entered which, I believe is a C++ standards no - no for the compiler.
Maybe something weird is happening with the optimizer or something?
Can anyone make any pertinent comments here, or suggestions? It just seems like some weird compiler behavior . The work around was to put the code and allocation in the curley brackets around averylargevariable1 in its own set of curley braces.