1. Template support The global specification should be expanded right after the specification definition (the golbal construct). The global variables and functions will be the private members of the data structure. In this case, the template of the data structure can be automatically passed to the variables and functions. Besides, as the public member of the function, all the interface check can access the specification variables and functions just as normal. 2. On-the-fly spec check For a check and action, they will be expanded right at the place where they are declared and will get executed when the inserted annotation gets executed. And the annotation is just a way to pass if the checks are satisfied. However, it is wrong because the annotation is also a type of atomic operation. For example, for a potential commit point and a later commit point check, they might be interleaved by another commit point. Therefore, we need to check in the specanalysis to see if the specific interleaving of annotation is "legal". 3. Happens-before initialization This concerns the place where we pass to the specanalysis the happens-before rules???? 4. To make implementation easier and the spec cleaner, we make a difference C and C++ programs. Since C does not support template and class, we require users to provide an entry point where we can initialize the sequential variables. By default, it's a C++ program, and everything is wrapped in an inner class because it can have easy initialization and template support. 5. We add @Interface_define construct in the specification. Basically, @Interface construct can be used in both interface declaration and interface definition, if they are not separated. However, if they are, then @Interface is used for the interface declaration and @Interface_define is for the interface definition. This is redundant information, but it makes the implementation much easier because we don't need to parse the C/C++ program.