Prolint Result messages?
Fri, 2008-10-10 09:47 — Duze
| Project: | Prolint Issue Tracker |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
When I run 'Lint Files' I get a few stange messages:
- Expected proparse version 3.1b, found 3.1c02
I've downloaded the latest ProParse and Prolint, why do I get this message??? Can't I use the latest ProLint with the latest ProParse??
- Multiple Lines with '8:50: unexpected token: no-undo'
Whats the reason for this message in Prolint??
Prolint Version 72
ProParse 3.1c02
Progress OpenEdge 10.1A230
- Login to post comments
Comments
#1
> When I run 'Lint Files' I get a few stange messages:
> - Expected proparse version 3.1b, found 3.1c02
> I've downloaded the latest ProParse and Prolint, why do I get this
> message??? Can't I use the latest ProLint with the latest ProParse??
>
Certainly you can, and our organization does. It's just warning you that you are on a proparse version that is different than the one last certified with prolint. It's a warning, not an error.
I've not run across that 8:50 error, however. I do have a very strange one. We invoke Prolint from within Roundtable. In all workspaces but one, it works fine. In the remaining workspace, we routinely get an error about passing the unknown value to a .dll. But what really makes it wierd is simply adding -debugalert so that we get the line number where the error is occurring makes the error go away. Removing -debugalert does not re-introduce the error -- until the next reboot. Then adding -debugalert makes it go away again. Heisenburg.
Glen
#2
Proparse writes error messages with file:line:column, so 8:50 would the the line and column where Proparse hits the unexpected token.
Is this perhaps 10.1C syntax that Proparse doesn't yet handle? In any case, it would be very helpful if you could create the smallest .p possible to trigger the error in Proparse (in this case, it might be a one-liner), and then submit that as an issue in the Proparse project.