Changeset c1c0efdb for doc/theses/jiada_liang_MMath/conclusion.tex

Timestamp:

Aug 8, 2024, 10:02:34 PM (2 months ago)

Author:

Peter A. Buhr <pabuhr@…>

Branches:

master

Children:

7568e5c

Parents:

11cced6

git-author:

Peter A. Buhr <pabuhr@…> (08/08/24 22:01:56)

git-committer:

Peter A. Buhr <pabuhr@…> (08/08/24 22:02:34)

Message:

last proofread of thesis

File:

• doc/theses/jiada_liang_MMath/conclusion.tex (modified) (3 diffs)

doc/theses/jiada_liang_MMath/conclusion.tex

@@ -13 +13 @@
 Enumeration traits define the meaning of an enumeration, allowing functions to be written that work on any enumeration, such as the reading and printing an enumeration.
 Using advanced duck typing, existing C enumerations can be extended so they work with all of the enumeration features, providing for legacy C code to be moved forward into the modern \CFA programming domain.
-Finally, I expanded the \CFA project's test suite with multiple enumeration features tests with respect to implicit conversions, control structures, inheritance, interaction with the polymorphic types, and the features built on top of enumeration traits.
+Finally, I expanded the \CFA project's test-suite with multiple enumeration features tests with respect to implicit conversions, control structures, inheritance, interaction with the polymorphic types, and the features built on top of enumeration traits.
 These tests ensure future \CFA work does not accidentally break the new enumeration system.
 
@@ -21 +21 @@
 \section{Future Work}
 
+The following are ideas to improve and extend the work in this thesis.
+\begin{enumerate}
+\item
 There are still corner cases being found in the current \CFA enumeration implementation.
-Fixing some of these corner cases requires changes to the \CFA resolver or extensions to \CFA, like compile-time constant-expression evaluation.
+Fixing some of these corner cases requires changes to the \CFA resolver or extensions to \CFA. %, like compile-time constant-expression evaluation.
 When these changes are made, it should be straightforward to update the \CFA enumeration implementation to work with them.
-
+\item
 Currently, some aspects of the enumeration trait system require explicitly including the file @enum.hfa@, which can lead to problems.
 It should be possible to have this file included implicitly by updating the \CFA prelude.
-
+\item
+There are multiple \CFA features being developed i parallel with enumerations.
+Two closely related features are iterator and namespace.
+Enumerations may have to be modified to dovetail with these features.
+For example, enumerating with range loops does not align with the current iterator design, so some changes will be necessary.
+\item
 C already provides @const@-style aliasing using the \emph{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 conceivable to extend it with types other than @int@.
@@ -42 +50 @@
 enum( wchar_t * ) { Jack = L"John" };
 \end{cfa}
-There are several new features have been proposed or are developing in parallel with enumerations.
-Two closely related features are iterator and namespace.
-
-Enumerating features, and range loops in particular, are currently implemented as loops unique to \CFA enumeration and do not align with the 
-general iterator pattern. They can be adapted to the iterator interface when it comes to maturity.
-
-Currently, \CFA implements a namespace feature for enumerated types only. There is recently a proposal by Andrew to 
-generalize the concept of namespace to other types. The enumeration scope will be revisited to follow the semantics 
-with other types. Also to improve the granularity of scope control, we propose the following extension:
+\item
+Currently enumeration scoping is all or nothing.
+In some cases, it might be useful to increase the scoping granularity to individual enumerators.
 \begin{cfa}
 enum E1 { @!@A, @^@B, C };
 enum E2 @!@ { @!@A, @^@B, C };
 \end{cfa}
-which provides a combination of scoped and unscoped enumerators.
+Here, @'!'@ means the enumerator is scoped, and @'^'@ means the enumerator is unscoped.
 For @E1@, @A@ is scoped; @B@ and @C@ are unscoped.
 For @E2@, @A@, and @C@ are scoped; @B@ is unscoped.
-Finding a use case is important to justify completing this extension.
+Finding a use case is important to justify this extension.
+\item
+An extension mentioned in \VRef{s:Ada} is using @typedef@ to create an enumerator alias.
+\begin{cfa}
+enum(int) RGB { @Red@, @Green@, Blue };
+enum(int) Traffic_Light { @Red@, Yellow, @Green@ };
+typedef RGB.Red OtherRed; // alias
+\end{cfa}
+\end{enumerate}