Issue 11730: text should mention optional writes in micro kdm and an example with a+1;                                                                                                                               (kdm-rtf)
Source: KDM Analytics (Dr. Nikolai Mansourov, nick@kdmanalytics.com)
Nature: Uncategorized Issue
Severity: 
Summary: text should mention optional writes in micro kdm and an example with a+1;
Resolution: 
Revised Text: 
Actions taken:
December 1, 2007: received issue
Discussion: 
Correct text:
Writes and single Flow are optional in most cases. Add word optional to the description of the
micro elements where appropriate.
Page 291 in front of table A.1
Optional Writes .. (no Writes corresponds to an expression statement, where the result of the
operation is ignored; otherwise the result should be stored into a DataElement, which can be
permanent, for example a StorableUnit with a kind other than “register”, a MemberUnit, an
ItemUnit or a ParameterUnit; or temporary, a StorableUnit with a “register” kind)
Optional single flow … (no Flow corresponds to the terminal action)
Page 292 in front of table A.2
Optional single Writes … (no Writes corresponds to an expression statement, where the result of
the operation is ignored)
Optional single flow …
Page 292 in front of table A.3:
Optional single Writes …
Optional single Flow …
Assign: optional single flow
Call: subsequently – an optional single flow …
MethodCall: subsequently an optional single flow …
PtrCall –subsequently an optional single flow to the next micro action is performed
VirtualCall – subsequently an optional single flow …
Condition (in the writes column) none
Return (in the writes column) none
Nop – optional single flow
Incr – optional single flow
Decr – optional single flow
Switch – an optional single flow
Page 297 Table A.5
Remove last column
Add description of the Control in front of the table:
Inputs – see table
Outputs – see table
Controls – optional single Flow to the next micro action (no Flow means a terminal action
element)
Move the semantics comment from the control column in the second column for the “New” micro
element:
This micro operation does not invoke the constructor of the new object;
FieldSelect, ChoiceSelect, Ptr, PtrSelect, ArraySelect, MemberSelect – optional Writes …Page 299 Table A.6
Remove last columns
Add description of the control in front of the table:
Inputs – see table
Outputs – see table
Controls – optional single Flow to the next micro action (no Flow means a terminal action
element)
InstanceOf, DynCase – optional Writes …
Page 300, table A.7
Remove last 2 columns
Add description of the writes and control in front of the table
Inputs – see table
Outputs – optional Writes to a DataElement (no Writes corresponds to an expression statement,
where the result of the operation is ignored; otherwise the result should be stored into a
DataElement, which can be permanent, for example a StorableUnit with a kind other than
“register”, a MemberUnit, an ItemUnit or a ParameterUnit; or temporary, a StorableUnit with a
“register” kind)
Controls – optional single Flow to the next micro action (no Flow means a terminal action
element)
Page 301, table A.8
Remove last 2 columns
Add description of the writes and control in front of the table
Inputs – see table
Outputs – optional Writes to a DataElement (no Writes corresponds to an expression statement,
where the result of the operation is ignored; otherwise the result should be stored into a
DataElement, which can be permanent, for example a StorableUnit with a kind other than
“register”, a MemberUnit, an ItemUnit or a ParameterUnit; or temporary, a StorableUnit with a
“register” kind)
Controls – optional single Flow to the next micro action (no Flow means a terminal action
element)
Page 302, table A.9
Remove last 2 columns
Add description of the writes and control in front of the table
Inputs – see table
Outputs – optional Writes to a DataElement (no Writes corresponds to an expression statement,
where the result of the operation is ignored; otherwise the result should be stored into a
DataElement, which can be permanent, for example a StorableUnit with a kind other than
“register”, a MemberUnit, an ItemUnit or a ParameterUnit; or temporary, a StorableUnit with a
“register” kind)
Controls – optional single Flow to the next micro action (no Flow means a terminal action
element)
Page 303, table A.10
Remove last 2 columns
Add description of the writes and control in front of the table
Inputs – see table
Outputs – optional Writes to a DataElement (no Writes corresponds to an expression statement,
where the result of the operation is ignored; otherwise the result should be stored into a
DataElement, which can be permanent, for example a StorableUnit with a kind other than
“register”, a MemberUnit, an ItemUnit or a ParameterUnit; or temporary, a StorableUnit with a
“register” kind) Controls – optional single Flow to the next micro action (no Flow means a terminal action
element)
End of Annotations:=====
ssues From: "Nikolai Mansourov" <nick@kdmanalytics.com> 

This is issue # 11730

text should mention optional writes in micro kdm and an example with a+1;