Turbo C++ 3.0 bugs

[Jim Leonard]

Jim Leonard wrote:
> I hate to mention the obvious, but have you tried tracing through the 
> code in a debugger to see what is actually happening?  If the first call 
> fails but the second call works, that is (in my experience) something 
> very easy to determine the cause of in a debugger.

(I forgot to clarify in my post that I meant a low-level debugger, stepping 
through assembler instructions, etc. -- not a C++ source symbolic debugger)
-- 
Jim Leonard (trixter at oldskool.org)                    http://www.oldskool.org/
Want to help an ambitious games project?             http://www.mobygames.com/
Or check out some trippy MindCandy at             http://www.mindcandydvd.com/