Home › projects › Prolint Issue Tracker

Issues for Prolint Issue Tracker

SummaryStatusPriorityCategoryLast updatedsort iconAssigned to
Detect unused USINGactivenormalfeature request7 years 21 weeks
function or non-void method should return a valueactivenormalfeature request8 years 16 weeks
new rule: cleanup-code can be moved into a finallyactivenormalfeature request8 years 19 weeks
request rule: SUPER should be last call in a 'tearactivenormalfeature request11 years 2 weeks
locate private methods that are never calledactivenormalfeature request11 years 3 weeks
database access not allowed in certain classesactivenormalfeature request11 years 3 weeks
BUFFER name must not match table nameactivenormalfeature request11 years 37 weeks
Give a warning when CURRENT-VALUE(SomeSequence) / activeminorfeature request11 years 46 weeks
"put-key-value" without "no-error"activenormalfeature request12 years 5 days
idea: configure Prolint rules by application layeractivenormalfeature request12 years 33 weeks
memory leaksactivenormalfeature request12 years 42 weeks
ambiguous findactivenormalfeature request12 years 42 weeks
temp-table defined without unique indexactivenormalfeature request12 years 42 weeks
probably bad roundingactivenormalfeature request12 years 42 weeks
no literal numbersactivenormalfeature request12 years 42 weeks
Dataserver portabilityactivenormalfeature request12 years 42 weeks
MESSAGE statement not closed with a periodactivenormalfeature request12 years 42 weeks
transaction scoped to comp.unit level?activenormalfeature request12 years 42 weeks
Find absolute path names in the codeactivenormalfeature request12 years 42 weeks
use EMPTY TEMP-TABLEactivenormalfeature request12 years 42 weeks
123next ›last »
#
Syndicate content