Analysis of plugins released packages, as taken from the Plugins area on 10th March 2004
The most abusive module is determined by counting the number of calls outside of Func in the module, with a 10X weighting factor for calls direct to TWiki that could have been done through Func. The results are then normalised to the range 0..1000.
Crawford, this transparency is great. It already prompted me to review and fix some Plugins. Hopefully other Plugin authors will follow.
I've attached the script(s) for your amusement. There are two scripts, extract_data.sh, which downloads (using wget) all the plugins, and extracts raw numbers for uses, and analyse_data.awk, which generates the web page.
provides everything that people need it to.
Also - it would be very useful to scan for all variables scanned for.
plugins are not checked into CVS, despite claiming that they are. It is rare that the released version corresponds with the version in CVS. My original version of the scripts worked directly from CVS, but I had to abandon that approach.
Scan for variables scanned for. That's what god gave you grep for, Martin.
But I appreciate what you are suggesting. If more plugins used CVS, then perhaps it would make sense to do something like this.
Is this a duplicate topic? I'm sure there is another topic with the output of the perl conformance analyser?