Debugging NewJ Applications
Within Visual C++ 7.1 or 6.0 IDE

Debug NewJ applications right inside the familiar Visual C++ 7.1 (Visual Studio .NET 2003) or Visual C++ 6.0 IDE (as shown). You debug NewJ applications just like any other C++ application. Set breakpoints, Step Into, Step Over, Step Out, Run to Cursor, Show Next Statement, and everything else. The screenshot shows the sample JGrep application being debugged at a breakpoint, along with the Watch window and Variables window, which contain both NewJ fundamental types and objects.

NewJ Single-language Debugging Much Simpler than Debugging Traditional Mixed-language Environments

Debugging NewJ applications is much easier than debugging mixed-language JNI applications that are part Java, part C/C++. There's no need to integrate complicated technologies like JNI or for special purpose mixed-language debuggers. With traditional approaches, even if your application is a 100% Java language application, you must still resort to mixed-language debugging in order to step into native methods in the Java API. With NewJ, you only have to use one language and one environment. It's native C++ code all the way down. This means you can step into and see every stitch of application or Java API code you're running through. This is a tremendous advantage for profiling and performance tuning. It's also invaluable for students and professional developers alike who are trying to see or learn how the Java API really works. 

Return to NewJ Library Features