Home › projects › Prolint Issue Tracker

Issues for Prolint Issue Tracker

SummaryStatusPriorityCategoryLast updatedAssigned tosort icon
temp-table defined without unique indexactivenormalfeature request12 years 42 weeks
functions (and ips) should not use variables in maactivenormalfeature request12 years 46 weeks
input blocking statement during database transactiactivenormalfeature request12 years 46 weeks
MESSAGE statement not closed with a periodactivenormalfeature request12 years 42 weeks
function or non-void method should return a valueactivenormalfeature request8 years 16 weeks
insufficient index information specified in WHERE-activenormalfeature request12 years 46 weeks
buffer in a FOR EACH statement is affected by IPactivenormalfeature request12 years 42 weeks
locate private methods that are never calledactivenormalfeature request11 years 3 weeks
no DEFINE statements between executable statementsactivenormalfeature request12 years 46 weeks
check if every RECORD_NAME and Field_Ref are qualiactivenormalfeature request12 years 42 weeks
idea: configure Prolint rules by application layeractivenormalfeature request12 years 33 weeks
check if each opened stream is closedactivenormalfeature request12 years 46 weeks
transaction-distinct: don't start a remote transacactivenormalfeature request12 years 42 weeks
probably bad roundingactivenormalfeature request12 years 42 weeks
widget X created but never deletedactivenormalfeature request12 years 46 weeks
transaction scoped to comp.unit level?activenormalfeature request12 years 42 weeks
new rule: cleanup-code can be moved into a finallyactivenormalfeature request8 years 19 weeks
abbreviation of database field names is not alloweactivenormalfeature request12 years 46 weeks
an IP should not access variables/buffers that areactivenormalfeature request12 years 42 weeks
BUFFER name must not match table nameactivenormalfeature request11 years 37 weeks
123next ›last »
#
Syndicate content