Home › projects › Prolint Issue Tracker

Issues for Prolint Issue Tracker

SummaryStatusPriorityCategorysort iconLast updatedAssigned to
check if every RECORD_NAME and Field_Ref are qualiactivenormalfeature request12 years 42 weeks
find "dead code"activenormalfeature request12 years 42 weeks
new rule: cleanup-code can be moved into a finallyactivenormalfeature request8 years 19 weeks
clean up inactivated codeactivenormalfeature request12 years 42 weeks
function or non-void method should return a valueactivenormalfeature request8 years 16 weeks
an IP should not access variables/buffers that areactivenormalfeature request12 years 42 weeks
Detect unused USINGactivenormalfeature request7 years 21 weeks
buffer in a FOR EACH statement is affected by IPactivenormalfeature request12 years 42 weeks
use EMPTY TEMP-TABLEactivenormalfeature request12 years 42 weeks
Find absolute path names in the codeactivenormalfeature request12 years 42 weeks
transaction scoped to comp.unit level?activenormalfeature request12 years 42 weeks
MESSAGE statement not closed with a periodactivenormalfeature request12 years 42 weeks
file 'checkin-event.p' calls function 'fnRtbGetLinfixedcriticalbug report10 years 26 weeksjurjen
core/Prolint.p gives error on get-row()fixednormalbug report10 years 22 weeks
namecheckfixednormalbug report10 years 21 weeksjurjen
rule tablename false positives when forward functiactivenormalbug report10 years 19 weeks
Check if propsuper is runningactivenormalbug report10 years 13 weeks
Varusage.SkipNewShared not implemented correctlyactivenormalbug report10 years 17 weeks
NOUNDO: false positive on dataset-handlesactivenormalbug report9 years 25 weeks
ABBREVKWD: false positive on field names assigned activenormalbug report9 years 25 weeks
« first‹ previous1234next ›last »
#
Syndicate content