Difference: ExecuteAfterPut (3 vs. 4)

Revision 42005-05-07 - KrisDeVolder

Line: 1 to 1
 
META TOPICPARENT name="DesignRulesRepository"

Execute After Put

Line: 22 to 22
 Adopting the design rule makes it feasible to check this property manually, or with a relatively straightforward intraprocedural analysis, because adherence to the desing rule limits the scope of the required analysis.
Added:
>
>

Related Design Rules

A similar design rule could be formulated for tyRuBa.tdbc.PreparedQuery.

Calls to PreparedQuery.put*(..) should always be followed by a call to PreparedQuery.executeQuery() within the same method context.

It may also be possible to distil both of these desing rules into a single rule.

 

Example

The following code contains a copy-paste bug: salaryFact never gets executed whereas employeeFact is executed twice.

View topic | History: r4 < r3 < r2 < r1 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback