Slashdot Mirror

← Back to Stories (view on slashdot.org)

Java Static Analysis And Custom Bug Detectors

Posted by ryuzaki0 on from the developerworks-ftl dept.

An anonymous reader writes "Java static analysis and custom bug detectors can be a very cost-effective way to improve software quality. By creating a detector for a known bug pattern, we can search for that bug pattern not only in the current code base for a specific project, but in any project, current or future. This article looks at how static analysis tools can change the way you manage software quality."

3 of 157 comments (clear)

  1. Re:People still use Java? by ErroneousBee · · Score: 0, Troll

    What, you maen someone created an application that wasnt a Java code IDE/editor/debugger/trace tool?

    Its 10 years later, and there are still no serious desktop applications written in Java. What is wrong with Java that causes all GUI apps to have the look, feel and performance of Jade Goodie?

    --
    **TODO** Steal someone elses sig.
  2. That's great... by Anonymous Coward · · Score: 0, Troll

    ... until Sun relases a new JRE and all your old aplications do not work at all anymore when users install the new JRE. Unmaintained applications die altogether or require constantly uninstalling and installing various JREs to run them as well as new ones. That's the biggest bug of all in Java and makes any bug tracking useless, and programming in Java pointless.

    C/C++ applications tend to work for decades and can be written to be far more reliably cross-platform.

    Java sucks bad, face it.

    1. Re:That's great... by handsome+b · · Score: 1, Troll

      You've clearly never ever developed anything in Java before. Perhaps you've heard the saying "Do not hold strong opinions about things you do not understand"... I've been developing a fairly large Java application for over 5 years, and the old beta versions that were written for Java 1.3 work unmodified on the Java 1.6 beta.

      Your statement is 100% false, face it.