Dear visitor, welcome to Jabaco - Community.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.
findbugs (Uni Maryland) utility
G'day everyone,
On a whim I ran findbugs over the jabaco.jar file. It found a horde (571 to be exact) of bugs (of which not all, but certainly some, may be severe). May I suggest that findbugs be downloaded and run in the presence of the source code?
Kind regards,
Bruce.
Wait, but wouldn't it be innacurate? Since Jabaco is a new language?
FindBugs
Hi all,
from my point of view, applying FindBugs to Jabaco.jar is a good idea. I tried the stand-alone Swing version of FindBugs. The list of findings is impressive.
However, it would be short-sighted to draw the direct conclusion "high number of errors = low quality of Jabaco". FindBugs is optimized to find potential problems in human-written code. Emphasis on "potential". Compiler-generated code might deliberately chose to use constructions which could be dangerous and difficult to maintain for typical developers.
The next step could be to cluster the warnings devised by FindBugs into severity levels. "real" problems should be solved, ideally by community volunteers. An excellent opportunity to get to know the Jabaco framework and to develop personal Java skills.
Best regards,
A1880
Tips, Tricks, Samples & Tutorials »
db2000 gpIPa [g]et [p]ublic [I]nternet [P]rotocol [a]ddress
(Jan 24th 2009, 7:16pm)