Code Count - Scans Libraries and Objects to Report Code Metrics

I have corrected the cause of the second error involving the PB 2025 Solution, but I need to do a little more testing. I will also address Jim Reese's suggestion to widen the columns to handle more than 999999 lines of code.

I appreciate you providing me with the exported source code for the global function, as it allowed me to identify the cause of the first issue you reported.

It appears you have manually created three override functions in a single function object (for a total of four global function definitions within a single global function object), which is extremely creative, I must admit. The prototype statement for the override function that works with Long values (there are two occurrences in the source) contains TWO spaces between the words "global" and "function". Although the PB compiler does a lexical scan and parsing of the source code which allows it to successfully compile the source, the Code Count app does not perform a lexical scan. For efficiency and performance, it depends heavily on seeing if a source code line begins with standard keyword phrases, such as "global function" (with one space). The presence of two spaces between these words causes Code Count to not correctly recognize the start of the code section that defines that particular override function.

If you remove the extra space (in both places) in the exported source code and re-import the function object, Code Count will be able to scan it successfully.

I will upload a new version of Code Count that address the Solution issue and the widened report columns in the very near future and I will reply here when it is available for download.

Hi John, attached is the function object source code. For the second type error I used the Solution type project. 

HTH

L.

Very nice. Very minor suggestion, although since you provide source, we can do it ourselves, but Source Lines column in the formatted reports (and perhaps others) should be widened, our total exceeds 1 million lines and gets clipped.

Thank you, Ludek, for letting me know about these issues!

In regards to the first issue where the comment line was flagged, would it be possible for you to provide the exported source for this Function object? If not, could you at least provide me with a portion of exported source around the line that was mentioned in the error? I really need to be able to see where this comment line appears in relation to other code blocks within the exported source in order to properly diagnose and correct the issue.

As for the second error, it would be helpful to know if the 2025 application code is in Workspace/pbl's format or in a Solution/file format. In the meantime, I will look into this error to try and determine what caused the array boundary to be exceeded.