Issues for Prolint Issue Tracker

SummaryStatussort iconPriorityCategoryLast updatedAssigned to
check for matching parameters in RUN statementsactivenormalfeature request12 years 46 weeks
rule tablename false positives when forward functiactivenormalbug report10 years 19 weeks
Find absolute path names in the codeactivenormalfeature request12 years 42 weeks
no DEFINE statements between executable statementsactivenormalfeature request12 years 46 weeks
Check if propsuper is runningactivenormalbug report10 years 13 weeks
transaction scoped to comp.unit level?activenormalfeature request12 years 42 weeks
check for capitalizing of keywordsactivenormalfeature request12 years 46 weeks
Varusage.SkipNewShared not implemented correctlyactivenormalbug report10 years 17 weeks
MESSAGE statement not closed with a periodactivenormalfeature request12 years 42 weeks
enforce the order of keywordsactivenormalfeature request12 years 46 weeks
NOUNDO: false positive on dataset-handlesactivenormalbug report9 years 25 weeks
Dataserver portabilityactivenormalfeature request12 years 42 weeks
abbreviation of database field names is not alloweactivenormalfeature request12 years 46 weeks
ABBREVKWD: false positive on field names assigned activenormalbug report9 years 25 weeks
no literal numbersactivenormalfeature request12 years 42 weeks
insufficient index information specified in WHERE-activenormalfeature request12 years 46 weeks
prolint says "ERROR: compile failed" for a new comactivenormalbug report8 years 36 weeks
probably bad roundingactivenormalfeature request12 years 42 weeks
type mismatch in parameter X when calling user-defactivenormalfeature request12 years 46 weeks
new rule: cleanup-code can be moved into a finallyactivenormalfeature request8 years 19 weeks
#
Syndicate content