Home › projects › Prolint Issue Tracker › Issues

core/Prolint.p gives error on get-row()

Tue, 2009-03-03 07:40 — Niek
Project:Prolint Issue Tracker
Component:Code
Category:bug report
Priority:normal
Assigned:Unassigned
Status:fixed
Description

When compilation "fails" with for example error 468, the compiler:error-status is set, error-status:num-messages is set, error-status:get-number(1) works but compiler:get-row(1) gives an error 4065 as if the call to the method is wrong?!?

Solution: Prolint.p should also skip compiler:error-number 468 (where it skips 4345 and 6430)

P.S. Logged a bug with Progress.


AttachmentSize
getrow.p485 bytes

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Tue, 2009-03-03 17:27 — jurjen
jurjen's picture

#1

Status:active» fixed

I have changed prolint.p so it ignores error 468 as you suggested (subversion revision 416).

The part in your text where you say "for example error 468" is bothering me... are there more error numbers where get-row() fails that we have to trap? If so I think its better if we just remove get-row at all from Prolint.


Tue, 2009-03-03 18:59 — Niek

#2

I also thought about that. I don't know.

Perhaps we should assign the line-number with no-error.
That way if the assign fails it stays ? or 0. Which is also fine since it is an error which occurs at no particular row.


Tue, 2009-03-03 22:09 — jurjen
jurjen's picture

#3

Simple yet effective. no-error added in revision 419 :-)