Proparse Error
Wed, 2007-06-27 20:59 — timtownsend
When running some source files through Prolint I get the error "IntegerIndex: No such index position" from Proparse. The file involved does compile OK with the Progress compiler. Any idea what this error means?
-Tim Townsend
- Login to post comments
Re: Proparse Error
Hi Tim, that could be triggered by a bug in one of the Prolint rules. Can you provide more details?
The "IntegerIndex" in Proparse allows an integer to be used in each node to keep track of which source (include) file that node came from. If a Prolint rule tries to look up a file name for a file number that's out of range, then Proparse would raise that error. (parserGetIndexFilename from Proparse's API)
Re: Proparse Error
The only prolint rule I am checking for at this point is "tablename". The error is the only output I get from prolint on certain programs. They do tend to have a complicated include structure, for example having the name of an include file defined in a preprocessor, in a previous include.
Anything else you need to know?
-Tim Townsend
Re: Proparse Error
I didn't see any use of parserGetIndexFilename in that rule, so nothing obvious jumps out. I'd need to be able to reproduce the error before I could figure it out, but Jurjen might have some ideas off the top of his head.
You might be able to test that Proparse is OK with your source file. You could try: Prolint Desktop -> Proparse Launcher -> Test Single. That might tell us whether to keep looking at Prolint, or if I have a bug in Proparse that I need to address.
Re: Proparse Error
Same error when I do this.
Press Esc to stop.
1 C:\dvtimmy-oe\code\server\jm\t-jmer.w parse
IntegerIndex: No such index position
Press Esc to close.
-Tim Townsend
Re: Proparse Error
Ah, OK. That's a Proparse issue then.
Please email me directly. I'll need enough example source code that I can re-create the error here.
(Whatever you send me, I have to be able to *compile* to confirm that I have it set up correctly.)
john at joanju dot com
Re: Proparse Error
I plead not guilty because parserGetIndexFilename is not used in any Prolint code.
But a fairly new feature in prolint/core/lintsuper.p tries to access the inherited class of each class (based on the usage of attribute 2100). This should only apply to *.cls files, in theory. Could this be where the trouble begins?
Re: Proparse Error
Yes, that's certainly possible. Hopefully Tim will let us know if he can reproduce the problem with Prolint taken out of the mix.