Changeset 31f4837 for doc/theses/jiada_liang_MMath/CFAenum.tex

Timestamp:

May 13, 2024, 10:26:59 AM (6 months ago)

Author:

JiadaL <j82liang@…>

Branches:

master

Children:

e6f1a4b

Parents:

acb33f15 (diff), ca4f2b2 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge branch 'master' of plg.uwaterloo.ca:software/cfa/cfa-cc

File:

• doc/theses/jiada_liang_MMath/CFAenum.tex (modified) (6 diffs)

doc/theses/jiada_liang_MMath/CFAenum.tex

@@ -11 +11 @@
 
 C already provides @const@-style aliasing using the unnamed enumerator \see{\VRef{s:TypeName}}, even if the name @enum@ is misleading (@const@ would be better).
-Given the existence of this form, it is straightforward to extend it with types other than integers.
+Given the existence of this form, it is straightforward to extend it with types other than @int@.
 \begin{cfa}
 enum E { Size = 20u, PI = 3.14159L, Jack = L"John" };
@@ -21 +21 @@
 
 
-\section{Enumerator Unscoping}
-\label{s:EnumeratorUnscoping}
-
-In C, unscoped enumerators presents a \newterm{naming problem} when multiple enumeration types appear in the same scope with duplicate enumerator names.
+\section{Enumerator Visibility}
+\label{s:EnumeratorVisibility}
+
+In C, unscoped enumerators present a \newterm{naming problem} when multiple enumeration types appear in the same scope with duplicate enumerator names.
 There is no mechanism in C to resolve these naming conflicts other than renaming one of the duplicates, which may be impossible.
 
@@ -33 +33 @@
 enum E1 { First, Second, Third, Fourth };
 enum E2 { @Fourth@, @Third@, @Second@, @First@ }; $\C{// same enumerator names}$
-E1 p() { return Third; }                                $\C{// correctly resolved duplicate names}$
+E1 p() { return Third; }                                $\C{// return}$
 E2 p() { return Fourth; }
 void foo() {
@@ -54 +54 @@
 enum RGB @!@ { Red, Green, Blue };
 \end{cfa}
-Now the enumerators \emph{must} be qualified with the associated enumeration.
+Now the enumerators \emph{must} be qualified with the associated enumeration type.
 \begin{cfa}
 Week week = @Week.@Mon;
@@ -68 +68 @@
 }
 \end{cfa}
-As in Section~\ref{s:EnumeratorUnscoping}, opening multiple scoped enumerations in a @with@ can result in duplicate enumeration names, but \CFA implicit type resolution and explicit qualification/casting handles ambiguities.
+As in Section~\ref{s:EnumeratorVisibility}, opening multiple scoped enumerations in a @with@ can result in duplicate enumeration names, but \CFA implicit type resolution and explicit qualification/casting handle ambiguities.
 
 \section{Enumeration Trait}
@@ -344 +344 @@
 \end{cfa}
 which make @Third == First@ and @Fourth == Second@, causing a compilation error because of duplicase @case@ clauses.
-To better match with programmer intuition, \CFA toggles between value and position semantics depneding on the language context.
+To better match with programmer intuition, \CFA toggles between value and position semantics depending on the language context.
 For conditional clauses and switch statments, \CFA uses the robust position implementation.
 \begin{cfa}