| 1 | \chapter{Introduction} |
|---|
| 2 | |
|---|
| 3 | The C programming language has had a wide-ranging impact on the design of software and programming languages. |
|---|
| 4 | In the 30 years since its first standardization, it has consistently been one of the most popular programming languages, with millions of lines of C code still in active use, and tens of thousands of trained programmers producing it. The TIOBE index\cite{TIOBE} tracks popularity of programming languages over time, and C has never dropped below second place: |
|---|
| 5 | |
|---|
| 6 | \begin{table}[h] |
|---|
| 7 | \caption[TIOBE index over time]{Current top 5 places in the TIOBE index averaged over years} \label{tiobe-table} |
|---|
| 8 | |
|---|
| 9 | \centering |
|---|
| 10 | \begin{tabular}{@{}cccccccc@{}} |
|---|
| 11 | & 2018 & 2013 & 2008 & 2003 & 1998 & 1993 & 1988 \\ |
|---|
| 12 | Java & 1 & 2 & 1 & 1 & 18 & -- & -- \\ |
|---|
| 13 | \textbf{C} & \textbf{2} & \textbf{1} & \textbf{2} & \textbf{2} & \textbf{1} & \textbf{1} & \textbf{1} \\ |
|---|
| 14 | \CC{} & 3 & 4 & 3 & 3 & 2 & 2 & 5 \\ |
|---|
| 15 | Python & 4 & 7 & 6 & 11 & 22 & 17 & -- \\ |
|---|
| 16 | \Csharp{} & 5 & 5 & 7 & 8 & -- & -- & -- \\ |
|---|
| 17 | \end{tabular} |
|---|
| 18 | \end{table} |
|---|
| 19 | |
|---|
| 20 | The impact of C on programming language design is also obvious from Table~\ref{tiobe-table}; with the exception of Python, all of the top five languages use C-like syntax and procedural control structures. |
|---|
| 21 | \CC{} is even a largely backwards-compatible extension of C, with development dating back nearly as far as C itself. |
|---|
| 22 | Though its lasting popularity and wide impact on programming language design point to the continued relevance of C, they also highlight the widespread desire of programmers for languages with more expressive power and programmer-friendly features; accommodating both low-impact maintenance of legacy C code and low-effort development of the software of the future is a difficult task for a single programming language. |
|---|
| 23 | |
|---|
| 24 | \CFA{}\footnote{Pronounced ``C-for-all'', and written \CFA{} or \CFL{}.} is an evolutionary modernization of the C programming language which aims to fulfill both these ends well. |
|---|
| 25 | \CFA{} both fixes existing design problems and adds multiple new features to C, including name overloading, user-defined operators, parametric-polymorphic routines, and type constructors and destructors, among others. |
|---|
| 26 | The new features make \CFA{} more powerful and expressive than C, while maintaining strong backward-compatibility with both C code and the procedural paradigm expected by C programmers. |
|---|
| 27 | However, these new features do impose a compile-time cost, particularly in the expression resolver, which must evaluate the typing rules of a significantly more complex type-system. |
|---|
| 28 | |
|---|
| 29 | This thesis is focused on making \CFA{} a more powerful and expressive language, both by adding new features to the \CFA{} type system and ensuring that both added and existing features can be efficiently implemented in \CFACC{}, the \CFA{} reference compiler. |
|---|
| 30 | Particular contributions of this work include design and implementation of |
|---|
| 31 | parametric-polymorphic (``generic'') types in a manner compatible with the existing polymorphism design of \CFA{} (Chapter~\ref{generic-chap}), a type environment data structure based on a novel variant of the union-find algorithm (Chapter~\ref{env-chap}), and a new expression resolution algorithm designed to quickly locate the optimal declarations for a \CFA{} expression (Chapter~\ref{resolution-chap}). |
|---|
| 32 | This expression resolution algorithm was designed with the aid of a purpose-built prototype system which encapsulates the essential aspects of the \CFA{} type system without incurring the technical debt of the existing system or the friction-inducing necessity of maintaining a working compiler; the goal of this prototype system was to discover effective heuristics to avoid performing unnecessary work in the process of locating the optimal \CFA{} expression resolution. |
|---|
| 33 | |
|---|
| 34 | Though the direction and validation of this work was fairly narrowly focused on the \CFA{} programming language, the tools used and results obtained should be of interest to a wider compiler and programming language design community. |
|---|
| 35 | In particular, with the addition of \emph{concepts} in \CCtwenty{}, conforming \CC{} compilers must support a model of type assertions very similar to that in \CFA{}, and the algorithmic techniques used in the expression resolution algorithm presented here may prove useful. |
|---|
| 36 | Type environments are also widely modelled in compiler implementations, particularly of functional languages, though also increasingly commonly in other languages (such as Rust) which perform type inference; the type environment presented here may be useful to those language implementers. |
|---|
