I've noticed some entries in the gtol.sym file that look like they have errors:
Line numbers are on the left. Notice the extra decimal point at the end of each line. It's the same in SW 2016 and SW 2017.
They do not seem to negatively impact anything from what I can tell. I see things like this and wonder how the software deals with such obvious screw ups. Somewhere in the code there is a workaround to deal with these 10 errors in a file with 7404 lines.
As a result of this screw up, I now have to put a workaround in my code so that when I try to turn '1.52.' into a number and it pukes, I can catch the error and remove the extraneous decimal point and try again.
Jim,
Thank you for pointing this out. Please see if you can have these filed as a low priority bug with your VAR. In the meantime, it is doubtful that we have special code to handing these specific cases, as the method to parse this file likely never even reads this extra period. If the extra period appeared in the middle of l line, it would cause issues. With the extra period at the end, it seems to be just outright ignored.