| Service / Report | Description | |
|---|---|---|
| Logical Source Statements (LSS) | The MUMPS equivalent of Source Lines Of Code (SLOC) of structured languages. [view sample] In MUMPS, entire routines are sometimes written on a single line, so SLOC has no meaning. | |
| Control Flow |
I generate two control flow reports. The first is plain text and with line
numbers, depth, routine name, explicit and implicit parameters, using
indented lines to indicate control.
[view text flow sample] The other report is a collection of HTML files that present the control flow as diagrams that may be followed using any web browser that supports JAVA. Each report has its advantages. The web enabled flow presents more information since it is not confined to a single line [view web flow samples]. |
|
| Data usage report | MUMPS equivalent of a set/use report but with much more information. It reports usage for both local and global data. [view sample] | |
| MUMPS to C++ | Approximately 95% of MUMPS code in a system can be transformed to C++ automatically. The code that cannot be transformed automatically is marked, and the parser decomposition of the code is inserted as comments. The code is also delimited with compiler switches so an error message (that may be turned off) is generated by the compiler. [view samples] | |
| Dollar text | Comments in MUMPS may be data or code. Any line may be referenced in mumps by using the $TEXT command. Lines that are the targets for $TEXT commands are extracted for use in other reports. The extracted data includes the file name, the line number within the file, the label associated with the line, the offset from the label, and the text from the line. A sample dtext file may be viewed here. | |
| MUMPS Complexity | Not much work has been done to analyze MUMPS complexity. But many of the complexity factors that apply to other computer languages can be applied to MUMPS. Follow this link to see how they may apply to MUMPS | |
|
To re-implement or to translate |
The decision to re-design and implement a new system, or whether to use an automated process to convert a system to another language can be very difficult. Follow this link to see some of the data to help make a good decision. | |
| Exception report | A report showing the syntax errors found in the code. It is not suprising to find errors in MUMPS code. MUMPS is interpreted, and the interpreter will not detect errors until the code is executed. | |
| Corrected code report | List of changes made to correct errors | |
| Naked references | A naked reference is a reference to a global data element without the name of the global data element that is being referenced. This report shows how naked references are resolved to one or more possibilities. | |
| Global Data Code | Just as relational databases support stored procedures, MUMPS code is stored in global data. The code is typically extracted using $PIECE, and sometimes concatenated with other extracted code, and finally executed using the XECUTE command. The sample global data code report was extracted from the global data file generated by a global save. The extracted routines are included in the analysis allowing a more complete representation of the system. | |
| Excluded files | List of files that were not included and the reason why each was not included in the analysis or transformation. | |
| Included files | List of files included in the analysis and/or transformation with file size information. |