It is currently Thu Nov 23, 2017 6:42 pm

All times are UTC - 8 hours [ DST ]

Post new topic Reply to topic  [ 2 posts ] 
Author Message
 Post subject: Any Tools for code metrics, quality or lbeautification?
PostPosted: Mon Aug 20, 2012 5:03 am 

Joined: Mon Aug 20, 2012 4:54 am
Posts: 2
Real Name: Greg
Began Programming in MUMPS: 01 Oct 2011

Are there any tools for checking code quality?
e.g. a way to parse MUMPS and use sonar tool (open source project)
or any other code quality tool

Or do the basics eg count lines of code and comments (e.g. CLOC)

Or do additional layout and style checks, and good programming checks
e.g. as per Lint for 'C'

And reverse engineering
ie creation of documentation - both textual and graphical (eg call trees)
as per javadoc, doxygen for Java
cflow for "C" to show a simple call tree

Ideally code to self document globals would be useful, is there a way to self document/explain the indexes in a global?

Or code beautification tools, to relayout code in a neat and consistent format.


Offline Profile  
 Post subject: Re: Any Tools for code metrics, quality or lbeautification?
PostPosted: Fri Mar 01, 2013 10:10 am 
User avatar

Joined: Wed Nov 17, 2010 4:02 pm
Posts: 68
Location: Houston TX
Real Name: David Whitten
Began Programming in MUMPS: 06 Jan 1982
I had never heard of Sonar as a code coverage tool. I looked it up, and apparently it is a tool that compares test cases with the code that it is being tested. This runs into the issue that very few people wrote test cases for MUMPS code in the past due to lack of space and resources. This could be changed, but until it is changed, sonar would not be a very useful tool.

I've never heard of CLOC, but have heard of SLOC (source lines of code). Generally the terse nature of MUMPS code means that counts of lines of code are pretty much meaningless when compared to other programming languages. The XINDEX program gives the number of bytes of code in a routine, but not the number of lines in a routine.

Some people consider XINDEX as something like a lint for MUMPS code. It is rather crude, and doesn't do live-code analysis, or def-use chains for variables, but it does give some warnings and errors on a routine.

There is a package from George James software called RE/M which does some reverse-engineering analysis of MUMPS code. It is something you have to purchase, the webpage
may give you some useful info about it.

Documentation re MUMPS routines in VistA can be stored in the ROUTINE File (#9.8) but very few people do that. It is also possible to comment the routine itself using semicolons (";")

Best Wishes,

Offline Profile  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 

All times are UTC - 8 hours [ DST ]

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Theme created