Home › forums › Prolint

Any issues with Prolint and Windows 2000?

Wed, 2009-02-11 21:19 — jmartin104

We run XP on 99% of our boxes with no issues. But we have one Win2k box that gets the following error when we try to lint a file:

"END CASE has no corresponding CASE statement." (5387)
c:\p4gl\tools\prolint\core\lintsuper.p could not understand line 153.

The code looks like it's correct.


‹ No RETURN in function New contributed rule fortranoper ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Wed, 2009-02-11 22:16 — jurjen
jurjen's picture

re: Any issues with Prolint and Windows 2000

That is a weird compiler error! Is it just Win2000 or is it also a different Progress version/patch on that win2k box?
I used to have a couple of different variations in vmware to test the compatibilty of Prolint, but my windows 2000 vmx is gone so I would have to build a new one. Can you tell me which Progress version it is?

Are you out of trouble when you replace this "END CASE" by simply "END"?


Thu, 2009-02-12 15:52 — jmartin104

Progress 9.1D Tell me about

Progress 9.1D

Tell me about it. It's just Win2k. If we change the END CASE to END, it then complains: "Unknown field or variable name grandchild".

We are planning to upgrade the box to either XP or Vista. Not sure when though.


Thu, 2009-02-12 16:20 — jurjen
jurjen's picture

re: prolint on win2k

yeah but, well, what about other sourcefiles? Since you are trying Prolint on this Windows 2000 box I suppose you are also compiling and running other Progress sourcefiles on this machine. Does the compiler go funny on other sourcefiles as well? Is it only prolint/core/lintsuper.p, or more prolint sourcefiles?

Could it be possible that the prolint sourcefiles, perhaps due to a mistake in the installer, contain characters that are not visible for the human eye but still confusing enough for the compiler? Could there possibly be a codepage issue, where the editor renders the sourcefile clean but the compiler still sees garbage? I have had that once with a sourcefile that was edited by a Japanese guy. But I do not code in any specific codepage as far as I am aware. So I would guess it's just a damaged sourcefile. Rename (dont delete) and install again, I'd say. And if that doesn't help simply format the c: drive ;-)