Home › projects › Prolint Issue Tracker

Issues for Prolint Issue Tracker

Summarysort iconStatusPriorityCategoryLast updatedAssigned to
enforce the order of keywordsactivenormalfeature request12 years 46 weeks
EXCLUSIVE-LOCK downgraded to SHARE-LOCK after tranactivenormalfeature request12 years 42 weeks
find "dead code"activenormalfeature request12 years 42 weeks
Find absolute path names in the codeactivenormalfeature request12 years 42 weeks
function or non-void method should return a valueactivenormalfeature request8 years 16 weeks
functions (and ips) should not use variables in maactivenormalfeature request12 years 46 weeks
Give a warning when CURRENT-VALUE(SomeSequence) / activeminorfeature request11 years 46 weeks
idea: configure Prolint rules by application layeractivenormalfeature request12 years 33 weeks
input blocking statement during database transactiactivenormalfeature request12 years 46 weeks
insufficient index information specified in WHERE-activenormalfeature request12 years 46 weeks
locate private methods that are never calledactivenormalfeature request11 years 3 weeks
memory in memptr X is never released with set-sizeactivenormalfeature request12 years 46 weeks
memory leaksactivenormalfeature request12 years 42 weeks
MESSAGE statement not closed with a periodactivenormalfeature request12 years 42 weeks
new rule: cleanup-code can be moved into a finallyactivenormalfeature request8 years 19 weeks
no DEFINE statements between executable statementsactivenormalfeature request12 years 46 weeks
no literal numbersactivenormalfeature request12 years 42 weeks
probably bad roundingactivenormalfeature request12 years 42 weeks
request rule: SUPER should be last call in a 'tearactivenormalfeature request11 years 2 weeks
Roundtable schema-update proceduresactivenormalfeature request12 years 42 weeks
« first‹ previous123next ›last »
#
Syndicate content