Linked by Thom Holwerda on Tue 12th Oct 2010 21:52 UTC
Java "Oracle and IBM today announced that the companies will collaborate to allow developers and customers to build and innovate based on existing Java investments and the OpenJDK reference implementation. Specifically, the companies will collaborate in the OpenJDK community to develop the leading open source Java environment."
Permalink for comment 444944
To read all comments associated with this story, please click here.
Member since:

Besides, many people who do know about these problems and generally write quality code occasionally make these errors and the reason is simple: Do something enough times and you'll make a mistake eventually. Why should we do something manually if it can be done automatically?
Also, you said that you did not experience any major pointer problems, but if you used a managed language, you wouldn't have any problems at all.

Ever heard of memory debugging tools like Valgrind ? Using them in testing is just as safe as using an interpreted language, but you don't need to perform slow checks *every time* a program is run.

Removing errors is part of the debugging phase. Doing it once the program is fully cleaned up is just unnecessary. If bugs go past the debugging phase, it's the debugging phase that is faulty for not stress-testing all aspects of the product.

Reply Parent Score: 3