Difference: ExecuteAfterPut (2 vs. 3)

Revision 32005-05-05 - KrisDeVolder

Line: 1 to 1

META TOPICPARENT	name="DesignRulesRepository"

Execute After Put

Added:

>
>

Execute After Put
- Context
- Description
- Rationale
- Related Design Rules
- Example
- Definition
  - JQuery
  - MetaL
  - AspectJ
  - HypotheticaL
- Ruminations

Context

An API specific design rule for the tyRuBa.tdbc package.

Line: 51 to 53

Definition

Changed:

<
<

JQuery

>
>

JQuery

This rule cannot be expressed in JQuery as is because it requires some dataflow.

Line: 81 to 83

NOT( calls(?methodContext, PreparedInsert.execute(), ?) )

Changed:

<
<

MetaL

>
>

MetaL

Yes, it can be expressed, but I don't know how. Somebody fill this in?

Changed:

<
<

AspectJ

>
>

Probably cannot be expressed in AspectJ. Perhaps it is possible to implement a dynamic checker for this, but it is complicated (need to track all instances put into during calling of a method and then check that they are all executed by the time the method exits).

Changed:

<
<

Hypothethical Wishful Thinking

>
>

HypotheticaL

Version 1: Makes use of explicit PCD that specify both calls must be on same instance and within the same method context.

View topic | History: r4 < r3 < r2 < r1 | More topic actions...