Context Navigation

-                      r17fdf6f
+                      r0c88135
 \begin{cfa}
 enum E { E1, E2, E3 };
 static const char * E_labels[3] = { "E1", "E2", "E3" };
 static const T E_values[3] = { t1, t2, t3 };
+const char * E_labels[3] = { "E1", "E2", "E3" };
+const T E_values[3] = { t1, t2, t3 };
 \end{cfa}
 The generated C enumeration has enumerator values that match \CFA enumerator positions because of C's auto-initialization.
 …
 so these expressions remain unchanged by \CFA-cc.
 Therefore, a \CFA enumeration variable has the same underlying representation as its generated C enumeration.
 This semantics implies a \CFA enumeration variable does not use memory, that @posn@ can use its underlying representation, and the label and value arrays take little storage.
+This semantics implies a \CFA enumeration variable uses the same storages as a C enumeration variable that @posn@ can use as its underlying representation, and the label and value arrays take little storage.
 It should be possible to eliminated the two arrays if unused, either by \CFA if local to a translation unit and unused, or by the linker if global but unreferenced.
 Also, the label and value arrays are declared @static@ and initialized with constants, so the arrays are allocated in the @.data@ section and initialized before program execution.

Note: See TracChangeset for help on using the changeset viewer.

Changeset 0c88135 for doc/theses/jiada_liang_MMath/CFAenum.tex