For some reason only the Project Analyser Report would open on my
machine. I think a great deal of the output is caused because it's only
looking at 10 files (that's the case for pretty much all of the dead
code reports). There were one or two other hints that might be useful
such as shortcircuiting nested if's where we have missed them, but
nothing earth-shattering that I could see.
Looks like it could be a useful tool for cleaning up seriously hacked
> -----Original Message-----
> From: Steve Boyle [mailto:boylesa(at)roselink(dot)co(dot)uk]
> Sent: 18 April 2003 02:32
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] pgAdmin II sample code metrics attached
> I've just been looking through the pgAdmin II src and have
> downloaded a trial bit of software from
> http://www.aivosto.com called Project > Analyser.
> Unfortunately the trial version only allows a maximum of 10
> files to be reviewed but I was very impressed with the speed
> of the analysis and the quality of the output.
> The analyser produces graphical and textual documentation of
> VB code and also produces quality metrics i.e. dead code, code depth,
> cohesion+coupling etc.
> I thought you (and the pgAdmin team) may be interested in the
> Steve Boyle
> P.S. Don't be alarmed by the 'dead procedure' references,
> most of them are probably due to only being able to select 10 files.
pgadmin-hackers by date
|Next:||From: Andreas Pflug||Date: 2003-04-18 18:58:55|
|Subject: Some pgadmin3 features|
|Previous:||From: Steve Boyle||Date: 2003-04-18 01:31:34|
|Subject: pgAdmin II sample code metrics attached|