Seems like good advice; this would allow running code inspections as part of the nightly build, which is has proved quite valuable with our C/C++ code. Still, performance is quite poor when navigating the results.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Glen Stampoutlzis Sent: Sunday, June 23, 2002 5:12 PM To: [EMAIL PROTECTED] Subject: [Eap-bugs] Re: My evaluation of the Code Review feature in build 629 "Rich Adili" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]... > 1. Excellent feature. Lots of useful stuff found. Several honest-too-gosh > lingering bugs found already and many probably bugs. > 2. Performance is terrible. Initial delay when parsing the project is > tolerable, but many delays are experienced when trying to navigate the > results and fix the problems. Very slow in this phase. > 3. Naive question: What are the judgment criteria used by the NPE-checking > feature? > Regarding point 2... Probably best to run it as a batch job overnight. This is an included batch file for this purpose. Regards, Glen Stampoultzis (TriNexus Pty Ltd) Fixed:+61 3 9753-6850 Mob:+61 (0)402 835 458 ICQ: 62722370 EMail: [EMAIL PROTECTED] URL's: http://jakarta.apache.org/poi, http://www.krysalis.org _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
