Issue 11719: representation of the sizeof (type) operator as opposed to sizeof (expr) op                                                                                                                             (kdm-rtf)
Source: KDM Analytics (Dr. Nikolai Mansourov, nick@kdmanalytics.com)
Nature: Uncategorized Issue
Severity: 
Summary: representation of the sizeof (type) operator as opposed to sizeof (expr) operator
     Sizeof should not have Reads ? Maybe addresses ? Maybe we need another micro action for sizeof type, 
     with a UsesType relation.
Resolution: 
Revised Text: 
Actions taken:
December 1, 2007: received issue
Discussion: 
There are two alternatives: just have UsesType to the Datatype, or allow also Reads to
DataElement (in the later case the processor should be able to calculate the type from the
expression first):
Sizeof Determines
the length
of a
DataElement
(based on
the
datatype) or
the length of
a Datatype
Reads
represents the
DataElement; or
UsesType
writes to
a
DataElement
Single
flow to
the next
micro
action
Disposition:
End of Annotations:=====
s is issue # 11719

representation of the sizeof (type) operator as opposed to sizeof (expr) op

representation of the sizeof (type) operator as opposed to sizeof (expr) operator
     Sizeof should not have Reads ? Maybe addresses ? Maybe we need another micro action for sizeof type, 
     with a UsesType relation.