Changeset cfc3e0f for doc/papers

Timestamp:

May 7, 2018, 1:40:24 PM (6 years ago)

Author:

Peter A. Buhr <pabuhr@…>

Branches:

ADT, aaron-thesis, arm-eh, ast-experimental, cleanup-dtors, deferred_resn, demangler, enum, forall-pointer-decay, jacob/cs343-translation, jenkins-sandbox, master, new-ast, new-ast-unique-expr, new-env, no_list, persistent-indexer, pthread-emulation, qualifiedEnum, with_gc

Children:

c5e5109

Parents:

01ff4e1

Message:

referee responses

Location:

doc/papers

Files:

• AMA/AMA-stix-1510051231000.zip (moved) (moved from doc/papers/AMA/AMA-stix.zip)
• AMA/AMA-stix/Documents/README.txt (modified) (1 diff)
• AMA/AMA-stix/ama/WileyNJD-AMA.bst (modified) (6 diffs)
• AMA/AMA-stix/ama/WileyNJD-v2.cls (modified) (6 diffs)
• general/.gitignore (modified) (1 diff)
• general/Makefile (modified) (2 diffs)
• general/Paper.tex (modified) (39 diffs)
• general/evaluation/timing.gp (modified) (1 diff)
• general/response (added)

doc/papers/AMA/AMA-stix/Documents/README.txt

@@ -13 +13 @@
 %   NJDnatbib.sty --> NJD natbib reference package.
 %   Stix-Fonts (folder) -->   Stix font files 
-
-%   MiKTeX 2.9 (Freeware software) is required to install STIX/LATO fonts
-%   Download MiKTeX installer & instructions from the below URLs
-        https://miktex.org/download
-        Instructions to install the basic MiKTeX installer
-        https://miktex.org/howto/install-miktex
-
-%   Execute(double click) --> Windows-Stix-fontinstaller.exe from Stix-Fonts folder (This EXE file will install fonts to local drive) (please rename Windows-Stix-fontinstaller.e_xe to Windows-Stix-fontinstaller.exe)
+%   Execute(double click) --> Windows-Stix-fontinstaller.exe from Stix-Fonts folder (This EXE file will install fonts to local drive)
 %   Still shows font error, please do the following
 %   Start-->run--> type "mo_edmin.exe" and press enter

doc/papers/AMA/AMA-stix/ama/WileyNJD-AMA.bst

@@ -502 +502 @@
       editor empty$
       { booktitle emphasize * }
-      { " " * format.editors * " " * booktitle emphasize * ", " * }
+    { " " * format.editors * " " * booktitle emphasize * ", " * }
       if$
     }
@@ -691 +691 @@
     { format.journal emphasize "journal" output.check
       format.date add.semicolon "year" output.check
+      blank.sep
       format.volume output
       format.number output
@@ -824 +825 @@
       new.block
       format.pages output
+      new.block
       organization output
+      new.block
       publisher output
       inproformat.date "year" output.check
@@ -863 +866 @@
     { new.block organization new.block address new.block.checkb
       organization output
+      new.block
       address output
     }
@@ -883 +887 @@
   new.block
   school "school" output.check
+  new.block
   address output
   format.date "year" output.check
@@ -927 +932 @@
   "PhD thesis" format.thesis.type output.nonnull
   school "school" output.check
+  new.block
   address output
   format.date "year" output.check

doc/papers/AMA/AMA-stix/ama/WileyNJD-v2.cls

@@ -484 +484 @@
 \if@STIXLargeOneCol%
 \RequirePackage[not1,notextcomp,lcgreekalpha]{stix}%
-%\usepackage[scaled]{helvet}
-%\renewcommand\familydefault{\sfdefault} 
 \usepackage[T1]{fontenc}
 \BXhsize=170mm%
@@ -528 +526 @@
 %\RequirePackage[not1,notextcomp,lcgreekalpha]{stix}%
 
-\captionsetup[figure]{labelformat=simple, labelsep=space, skip=10pt, labelfont=bf}
-\captionsetup[table]{labelformat=simple, labelsep=space, skip=10pt, labelfont=bf}
-\renewcommand{\thefigure}{\arabic{figure}}
-
-\renewcommand{\thetable}{\arabic{table}}
+\captionsetup[figure]{labelformat=simple, labelsep=none, skip=10pt, labelfont=bf}
+\captionsetup[table]{labelformat=simple, labelsep=none, skip=10pt, labelfont=bf}
+\renewcommand{\thefigure}{\arabic{figure}\enspace }
+
+\renewcommand{\thetable}{\arabic{table}\enspace }
 
 \renewcommand\figurename{\textbf{FIGURE}}%%
@@ -1414 +1412 @@
 \gdef\@stix@font@defn{%
   %
-%  \def\infoboxfont{\fontfamily{tim}\fontsize{8}{8}\selectfont}%
+  \def\infoboxfont{\fontfamily{tim}\fontsize{8}{8}\selectfont}%
   %
-%  \def\watermarkfont{\reset@font\fontfamily{\ffdefault}\fontsize{45}{45}\bfseries\selectfont}
+  \def\watermarkfont{\reset@font\fontfamily{\ffdefault}\fontsize{45}{45}\bfseries\selectfont}
   %
   \def\pagenumfont{\rmfamily\fontsize{7}{9}\bfseries\selectfont}%
@@ -1429 +1427 @@
   \def\arttypefont{\rmfamily\fontsize{9}{9}\fontseries{b}\selectfont}%
   \def\SParttypefont{\rmfamily\fontsize{9}{12}\fontseries{b}\selectfont}%
-  \def\titlefont{\rmfamily\fontsize{18}{23}\bfseries\selectfont\leftskip\z@\rightskip\z@ plus1fil}%
+  \def\titlefont{\rmfamily\fontsize{18}{23}\bfseries\selectfont\leftskip\z@\rightskip\z@ plus1fil\let\mathbcal\titmathbcal}%
   \def\subtitlefont{\rmfamily\fontsize{16}{21}\bfseries\selectfont\leftskip\z@\rightskip\z@ plus1fil}%
   \def\Authorfont{\rmfamily\fontsize{12}{18}\selectfont\leftskip\z@\rightskip\z@ plus1fil}%
@@ -1484 +1482 @@
 \gdef\@lato@font@defn{%
   %
-%  \def\infoboxfont{\fontfamily{tim}\fontsize{8}{8}\selectfont}%
+  \def\infoboxfont{\fontfamily{tim}\fontsize{8}{8}\selectfont}%
   %
-%  \def\watermarkfont{\reset@font\fontfamily{\ffdefault}\fontsize{45}{45}\bfseries\selectfont}
+  \def\watermarkfont{\reset@font\fontfamily{\ffdefault}\fontsize{45}{45}\bfseries\selectfont}
   %
   \def\pagenumfont{\rmfamily\fontsize{7}{9}\bfseries\selectfont}%
@@ -3249 +3247 @@
     \fi
   \fi%
-  \renewcommand\thefigure{\@Alph\c@section\arabic{figure}}%
-  \renewcommand\thetable{\@Alph\c@section\arabic{table}}%
+  \renewcommand\thefigure{\@Alph\c@section\arabic{figure}\enspace }%
+  \renewcommand\thetable{\@Alph\c@section\arabic{table}\enspace }%
   \renewcommand\theequation{\@Alph\c@section\arabic{equation}}%
 }{%

doc/papers/general/.gitignore

@@ -8 +8 @@
 Paper.out.ps
 WileyNJD-AMA.bst
+evaluation.zip

doc/papers/general/Makefile

@@ -45 +45 @@
         @rm -frv ${DOCUMENT} ${BASE}.ps WileyNJD-AMA.bst ${BASE}.out.ps ${Build}
 
+evaluation.zip :
+        zip -x evaluation/.gitignore  -x evaluation/timing.xlsx -x evaluation/timing.dat -r evaluation.zip evaluation
+
 # File Dependencies #
 
@@ -66 +69 @@
 ## Define the default recipes.
 
-${Build}:
+${Build} :
         mkdir -p ${Build}
 
-${BASE}.out.ps: ${Build}
+${BASE}.out.ps : ${Build}
         ln -fs ${Build}/Paper.out.ps .
 
-WileyNJD-AMA.bst:
+WileyNJD-AMA.bst :
         ln -fs ../AMA/AMA-stix/ama/WileyNJD-AMA.bst .
 

doc/papers/general/Paper.tex

@@ -174 +174 @@
 \lstMakeShortInline@%
 
+\let\OLDthebibliography\thebibliography
+\renewcommand\thebibliography[1]{
+  \OLDthebibliography{#1}
+  \setlength{\parskip}{0pt}
+  \setlength{\itemsep}{4pt plus 0.3ex}
+}
 
 \title{\texorpdfstring{\protect\CFA : Adding Modern Programming Language Features to C}{Cforall : Adding Modern Programming Language Features to C}}
@@ -191 +197 @@
 The C programming language is a foundational technology for modern computing with millions of lines of code implementing everything from commercial operating-systems to hobby projects.
 This installation base and the programmers producing it represent a massive software-engineering investment spanning decades and likely to continue for decades more.
-Nevertheless, C, first standardized over thirty years ago, lacks many features that make programming in more modern languages safer and more productive.
-The goal of the \CFA project is to create an extension of C that provides modern safety and productivity features while still ensuring strong backwards compatibility with C and its programmers.
+Nevertheless, C, first standardized almost fourty years ago, lacks many features that make programming in more modern languages safer and more productive.
+
+The goal of the \CFA project (pronounced ``C-for-all'') is to create an extension of C that provides modern safety and productivity features while still ensuring strong backwards compatibility with C and its programmers.
 Prior projects have attempted similar goals but failed to honour C programming-style; for instance, adding object-oriented or functional programming with garbage collection is a non-starter for many C developers.
 Specifically, \CFA is designed to have an orthogonal feature-set based closely on the C programming paradigm, so that \CFA features can be added \emph{incrementally} to existing C code-bases, and C programmers can learn \CFA extensions on an as-needed basis, preserving investment in existing code and programmers.
@@ -226 +233 @@
 Love it or hate it, C is extremely popular, highly used, and one of the few systems languages.
 In many cases, \CC is often used solely as a better C.
-Nevertheless, C, first standardized over thirty years ago, lacks many features that make programming in more modern languages safer and more productive.
+Nevertheless, C, first standardized almost fourty years ago~\cite{ANSI89:C}, lacks many features that make programming in more modern languages safer and more productive.
 
 \CFA (pronounced ``C-for-all'', and written \CFA or Cforall) is an evolutionary extension of the C programming language that adds modern language-features to C, while maintaining both source and runtime compatibility with C and a familiar programming model for programmers.
@@ -324 +331 @@
 int max( int a, int b ) { return a < b ? b : a; }  $\C{// (3)}$
 double max( double a, double b ) { return a < b ? b : a; }  $\C{// (4)}\CRT$
-max( 7, -max );                                         $\C[2.75in]{// uses (3) and (1), by matching int from constant 7}$
+max( 7, -max );                                         $\C{// uses (3) and (1), by matching int from constant 7}$
 max( max, 3.14 );                                       $\C{// uses (4) and (2), by matching double from constant 3.14}$
-max( max, -max );                                       $\C{// ERROR: ambiguous}$
-int m = max( max, -max );                       $\C{// uses (3) and (1) twice, by matching return type}\CRT$
+max( max, -max );                                       $\C{// ERROR, ambiguous}$
+int m = max( max, -max );                       $\C{// uses (3) and (1) twice, by matching return type}$
 \end{cfa}
 
@@ -336 +343 @@
 As is shown later, there are a number of situations where \CFA takes advantage of available type information to disambiguate, where other programming languages generate ambiguities.
 
-\Celeven added @_Generic@ expressions, which is used in preprocessor macros to provide a form of ad-hoc polymorphism;
+\Celeven added @_Generic@ expressions~\cite[\S~6.5.1.1]{C11}, which is used with preprocessor macros to provide ad-hoc polymorphism;
 however, this polymorphism is both functionally and ergonomically inferior to \CFA name overloading. 
 The macro wrapping the generic expression imposes some limitations;
@@ -369 +376 @@
 \begin{cfa}
 forall( otype T `| { T ?+?(T, T); }` ) T twice( T x ) { return x `+` x; }  $\C{// ? denotes operands}$
-int val = twice( twice( 3.7 ) );
+int val = twice( twice( 3.7 ) );  $\C{// val == 14}$
 \end{cfa}
 which works for any type @T@ with a matching addition operator.
 The polymorphism is achieved by creating a wrapper function for calling @+@ with @T@ bound to @double@, then passing this function to the first call of @twice@.
 There is now the option of using the same @twice@ and converting the result to @int@ on assignment, or creating another @twice@ with type parameter @T@ bound to @int@ because \CFA uses the return type~\cite{Cormack81,Baker82,Ada} in its type analysis.
-The first approach has a late conversion from @double@ to @int@ on the final assignment, while the second has an eager conversion to @int@.
+The first approach has a late conversion from @double@ to @int@ on the final assignment, while the second has an early conversion to @int@.
 \CFA minimizes the number of conversions and their potential to lose information, so it selects the first approach, which corresponds with C-programmer intuition.
 
@@ -420 +427 @@
 \begin{cfa}
 forall( otype T | { int ?<?( T, T ); } ) void qsort( const T * arr, size_t size ) { /* use C qsort */ }
-{
+int main() {
         int ?<?( double x, double y ) { return x `>` y; } $\C{// locally override behaviour}$
-        qsort( vals, size );                                    $\C{// descending sort}$
+        qsort( vals, 10 );                                                      $\C{// descending sort}$
 }
 \end{cfa}
@@ -534 +541 @@
 \begin{cquote}
 \lstDeleteShortInline@%
-\begin{tabular}{@{}l|@{\hspace{2\parindentlnth}}l@{}}
+\begin{tabular}{@{}l|@{\hspace{\parindentlnth}}l@{}}
 \begin{cfa}
 forall( otype R, otype S ) struct pair {
@@ -578 +585 @@
 \begin{cfa}
 struct _pair_conc0 {
-        const char * first;
-        int second;
+        const char * first;  int second;
 };
 \end{cfa}
@@ -587 +593 @@
 \begin{cfa}
 struct _pair_conc1 {
-        void * first;
-        void * second;
+        void * first, * second;
 };
 \end{cfa}
@@ -645 +650 @@
 \begin{cquote}
 \lstDeleteShortInline@%
-\begin{tabular}{@{}l@{\hspace{2\parindentlnth}}l@{}}
+\begin{tabular}{@{}l|@{\hspace{\parindentlnth}}l@{}}
 \begin{cfa}
 forall( dtype Unit ) struct scalar { unsigned long value; };
@@ -661 +666 @@
                                                         half_marathon;
 scalar(litres) two_pools = pool + pool;
-`marathon + pool;`      // compilation ERROR
+`marathon + pool;`      // ERROR, mismatched types
 \end{cfa}
 \end{tabular}
@@ -1006 +1011 @@
 \begin{cfa}
 forall( dtype T0, dtype T1 | sized(T0) | sized(T1) ) struct _tuple2 {
-        T0 field_0;                                                             $\C{// generated before the first 2-tuple}$
-        T1 field_1;
+        T0 field_0;  T1 field_1;                                        $\C{// generated before the first 2-tuple}$
 };
 _tuple2(int, int) f() {
         _tuple2(double, double) x;
         forall( dtype T0, dtype T1, dtype T2 | sized(T0) | sized(T1) | sized(T2) ) struct _tuple3 {
-                T0 field_0;                                                     $\C{// generated before the first 3-tuple}$
-                T1 field_1;
-                T2 field_2;
+                T0 field_0;  T1 field_1;  T2 field_2;   $\C{// generated before the first 3-tuple}$
         };
         _tuple3(int, double, int) y;
 }
 \end{cfa}
-{\sloppy
-Tuple expressions are then simply converted directly into compound literals, \eg @[5, 'x', 1.24]@ becomes @(_tuple3(int, char, double)){ 5, 'x', 1.24 }@.
-\par}%
+Tuple expressions are then converted directly into compound literals, \eg @[5, 'x', 1.24]@ becomes @(_tuple3(int, char,@ @double)){ 5, 'x', 1.24 }@.
 
 \begin{comment}
@@ -1105 +1105 @@
 \begin{cquote}
 \lstDeleteShortInline@%
-\begin{tabular}{@{}l@{\hspace{2\parindentlnth}}l@{}}
+\begin{tabular}{@{}l|@{\hspace{2\parindentlnth}}l@{}}
 \multicolumn{1}{c@{\hspace{2\parindentlnth}}}{\textbf{\CFA}}    & \multicolumn{1}{c}{\textbf{C}}        \\
 \begin{cfa}
@@ -1174 +1174 @@
 \centering
 \lstDeleteShortInline@%
-\begin{tabular}{@{}l@{\hspace{2\parindentlnth}}l@{}}
-\multicolumn{1}{c@{\hspace{2\parindentlnth}}}{\textbf{\CFA}}    & \multicolumn{1}{c}{\textbf{C}}        \\
+\begin{tabular}{@{}l|@{\hspace{\parindentlnth}}l@{}}
+\multicolumn{1}{c|@{\hspace{\parindentlnth}}}{\textbf{\CFA}}    & \multicolumn{1}{c}{\textbf{C}}        \\
 \begin{cfa}
 `choose` ( day ) {
@@ -1220 +1220 @@
 \centering
 \lstDeleteShortInline@%
-\begin{tabular}{@{}l@{\hspace{2\parindentlnth}}l@{}}
-\multicolumn{1}{c@{\hspace{2\parindentlnth}}}{\textbf{non-terminator}}  & \multicolumn{1}{c}{\textbf{target label}}     \\
+\begin{tabular}{@{}l|@{\hspace{\parindentlnth}}l@{}}
+\multicolumn{1}{c|@{\hspace{\parindentlnth}}}{\textbf{non-terminator}}  & \multicolumn{1}{c}{\textbf{target label}}     \\
 \begin{cfa}
 choose ( ... ) {
@@ -1264 +1264 @@
 \begin{figure}
 \lstDeleteShortInline@%
-\begin{tabular}{@{\hspace{\parindentlnth}}l@{\hspace{\parindentlnth}}l@{\hspace{\parindentlnth}}l@{}}
-\multicolumn{1}{@{\hspace{\parindentlnth}}c@{\hspace{\parindentlnth}}}{\textbf{\CFA}}   & \multicolumn{1}{@{\hspace{\parindentlnth}}c}{\textbf{C}}      \\
+\begin{tabular}{@{\hspace{\parindentlnth}}l|@{\hspace{\parindentlnth}}l@{\hspace{\parindentlnth}}l@{}}
+\multicolumn{1}{@{\hspace{\parindentlnth}}c|@{\hspace{\parindentlnth}}}{\textbf{\CFA}}  & \multicolumn{1}{@{\hspace{\parindentlnth}}c}{\textbf{C}}      \\
 \begin{cfa}
 `LC:` {
@@ -1349 +1349 @@
 \subsection{Exception Handling}
 
-The following framework for \CFA exception handling is in place, excluding some runtime type-information and virtual functions.
+The following framework for \CFA exception-handling is in place, excluding some runtime type-information and virtual functions.
 \CFA provides two forms of exception handling: \newterm{fix-up} and \newterm{recovery} (see Figure~\ref{f:CFAExceptionHandling})~\cite{Buhr92b,Buhr00a}.
 Both mechanisms provide dynamic call to a handler using dynamic name-lookup, where fix-up has dynamic return and recovery has static return from the handler.
@@ -1360 +1360 @@
 \begin{cquote}
 \lstDeleteShortInline@%
-\begin{tabular}{@{}l@{\hspace{2\parindentlnth}}l@{}}
-\multicolumn{1}{c@{\hspace{2\parindentlnth}}}{\textbf{Resumption}}      & \multicolumn{1}{c}{\textbf{Termination}}      \\
+\begin{tabular}{@{}l|@{\hspace{\parindentlnth}}l@{}}
+\multicolumn{1}{c|@{\hspace{\parindentlnth}}}{\textbf{Resumption}}      & \multicolumn{1}{c}{\textbf{Termination}}      \\
 \begin{cfa}
 `exception R { int fix; };`
@@ -1852 +1852 @@
 This provides a much more orthogonal design for library implementors, obviating the need for workarounds such as @std::reference_wrapper@.
 Secondly, \CFA references are rebindable, whereas \CC references have a fixed address.
-\newsavebox{\LstBox}
-\begin{lrbox}{\LstBox}
-\lstset{basicstyle=\footnotesize\linespread{0.9}\sf}
-\begin{cfa}
-int & r = *new( int );
-...                                                                                     $\C{// non-null reference}$
-delete &r;                                                                      $\C{// unmanaged (programmer) memory-management}$
-r += 1;                                                                         $\C{// undefined reference}$
-\end{cfa}
-\end{lrbox}
 Rebinding allows \CFA references to be default-initialized (\eg to a null pointer\footnote{
-While effort has been made into non-null reference checking in \CC and Java, the exercise seems moot for any non-managed languages (C/\CC), given that it only handles one of many different error situations:
-\begin{cquote}
-\usebox{\LstBox}
-\end{cquote}
-}%
-) and point to different addresses throughout their lifetime, like pointers.
+While effort has been made into non-null reference checking in \CC and Java, the exercise seems moot for any non-managed languages (C/\CC), given that it only handles one of many different error situations, \eg using a pointer after its storage is deleted.}) and point to different addresses throughout their lifetime, like pointers.
 Rebinding is accomplished by extending the existing syntax and semantics of the address-of operator in C.
 
@@ -1880 +1865 @@
 \begin{itemize}
 \item
-if @R@ is an rvalue of type {@T &@$_1 \cdots$@ &@$_r$} where $r \ge 1$ references (@&@ symbols) than @&R@ has type {@T `*`&@$_{\color{red}2} \cdots$@ &@$_{\color{red}r}$}, \\ \ie @T@ pointer with $r-1$ references (@&@ symbols).
+if @R@ is an rvalue of type {@T &@$_1 \cdots$@ &@$_r$} where $r \ge 1$ references (@&@ symbols) then @&R@ has type {@T `*`&@$_{\color{red}2} \cdots$@ &@$_{\color{red}r}$}, \\ \ie @T@ pointer with $r-1$ references (@&@ symbols).
         
 \item
@@ -1914 +1899 @@
 \end{cfa}
 This allows complex values to be succinctly and efficiently passed to functions, without the syntactic overhead of explicit definition of a temporary variable or the runtime cost of pass-by-value.
-\CC allows a similar binding, but only for @const@ references; the more general semantics of \CFA are an attempt to avoid the \newterm{const hell} problem, in which addition of a @const@ qualifier to one reference requires a cascading chain of added qualifiers.
+\CC allows a similar binding, but only for @const@ references; the more general semantics of \CFA are an attempt to avoid the \newterm{const poisoning} problem~\cite{Taylor10}, in which addition of a @const@ qualifier to one reference requires a cascading chain of added qualifiers.
 
 
@@ -1928 +1913 @@
 \begin{tabular}{@{}l@{\hspace{3em}}l|l@{}}
 \multicolumn{1}{c@{\hspace{3em}}}{\textbf{C Type Nesting}}      & \multicolumn{1}{c|}{\textbf{C Implicit Hoisting}}     & \multicolumn{1}{c}{\textbf{\CFA}}     \\
-\hline
 \begin{cfa}
 struct S {
@@ -2259 +2243 @@
         W w, heavy = { 20 };
         w = 155|_lb|;
-        w = 0b1111|_lb|;       // error, binary unsupported
+        // binary unsupported
         w = 0${\color{red}\LstBasicStyle{'}}$233|_lb|;          // quote separator
         w = 0x9b|_kg|;
@@ -2307 +2291 @@
 \begin{cquote}
 \lstDeleteShortInline@%
-\begin{tabular}{@{}l@{\hspace{2\parindentlnth}}l@{}}
-\multicolumn{1}{c@{\hspace{2\parindentlnth}}}{\textbf{\CFA}}    & \multicolumn{1}{c}{\textbf{C}}        \\
+\begin{tabular}{@{}l@{\hspace{\parindentlnth}}l@{}}
+\multicolumn{1}{c@{\hspace{\parindentlnth}}}{\textbf{\CFA}}     & \multicolumn{1}{c}{\textbf{C}}        \\
 \begin{cfa}
 MIN
-
 MAX
-
 PI
 E
@@ -2319 +2301 @@
 &
 \begin{cfa}
-SCHAR_MIN, CHAR_MIN, SHRT_MIN, INT_MIN, LONG_MIN,
-        LLONG_MIN, FLT_MIN, DBL_MIN, LDBL_MIN
-SCHAR_MAX, UCHAR_MAX, SHRT_MAX, INT_MAX, LONG_MAX,
-        LLONG_MAX, FLT_MAX, DBL_MAX, LDBL_MAX
+CHAR_MIN, SHRT_MIN, INT_MIN, LONG_MIN, LLONG_MIN, FLT_MIN, DBL_MIN, LDBL_MIN
+UCHAR_MAX, SHRT_MAX, INT_MAX, LONG_MAX, LLONG_MAX, FLT_MAX, DBL_MAX, LDBL_MAX
 M_PI, M_PIl
 M_E, M_El
@@ -2441 +2421 @@
 
 \begin{table}
+\caption{Storage-Management Operations}
+\label{t:StorageManagementOperations}
 \centering
 \lstDeleteShortInline@%
@@ -2460 +2442 @@
 \lstDeleteShortInline~%
 \lstMakeShortInline@%
-\caption{Storage-Management Operations}
-\label{t:StorageManagementOperations}
 \end{table}
 
@@ -2589 +2569 @@
 \end{cquote}
 There is a weak similarity between the \CFA logical-or operator and the Shell pipe-operator for moving data, where data flows in the correct direction for input but the opposite direction for output.
-
+\begin{comment}
 The implicit separator character (space/blank) is a separator not a terminator.
 The rules for implicitly adding the separator are:
@@ -2608 +2588 @@
 }%
 \end{itemize}
+\end{comment}
 There are functions to set and get the separator string, and manipulators to toggle separation on and off in the middle of output.
 
@@ -2656 +2637 @@
 
 
-\section{Evaluation}
+\section{Polymorphism Evaluation}
 \label{sec:eval}
 
-Though \CFA provides significant added functionality over C, these features have a low runtime penalty.
-In fact, \CFA's features for generic programming can enable faster runtime execution than idiomatic @void *@-based C code.
-This claim is demonstrated through a set of generic-code-based micro-benchmarks in C, \CFA, and \CC (see stack implementations in Appendix~\ref{sec:BenchmarkStackImplementations}).
+\CFA adds parametric polymorphism to C.
+A runtime evaluation is performed to compare the cost of alternative styles of polymorphism.
+The goal is to compare just the underlying mechanism for implementing different kinds of polymorphism.
+% Though \CFA provides significant added functionality over C, these features have a low runtime penalty.
+% In fact, it is shown that \CFA's generic programming can enable faster runtime execution than idiomatic @void *@-based C code.
+The experiment is a set of generic-stack micro-benchmarks~\cite{CFAStackEvaluation} in C, \CFA, and \CC (see implementations in Appendix~\ref{sec:BenchmarkStackImplementations}).
 Since all these languages share a subset essentially comprising standard C, maximal-performance benchmarks should show little runtime variance, differing only in length and clarity of source code.
 A more illustrative comparison measures the costs of idiomatic usage of each language's features.
@@ -2692 +2676 @@
 \end{figure}
 
-The structure of each benchmark implemented is: C with @void *@-based polymorphism, \CFA with the presented features, \CC with templates, and \CC using only class inheritance for polymorphism, called \CCV.
+The structure of each benchmark implemented is: C with @void *@-based polymorphism, \CFA with parametric polymorphism, \CC with templates, and \CC using only class inheritance for polymorphism, called \CCV.
 The \CCV variant illustrates an alternative object-oriented idiom where all objects inherit from a base @object@ class, mimicking a Java-like interface;
 hence runtime checks are necessary to safely down-cast objects.
 The most notable difference among the implementations is in memory layout of generic types: \CFA and \CC inline the stack and pair elements into corresponding list and pair nodes, while C and \CCV lack such a capability and instead must store generic objects via pointers to separately-allocated objects.
-Note that the C benchmark uses unchecked casts as there is no runtime mechanism to perform such checks, while \CFA and \CC provide type-safety statically.
+Note, the C benchmark uses unchecked casts as C has no runtime mechanism to perform such checks, while \CFA and \CC provide type-safety statically.
 
 Figure~\ref{fig:eval} and Table~\ref{tab:eval} show the results of running the benchmark in Figure~\ref{fig:BenchmarkTest} and its C, \CC, and \CCV equivalents.
@@ -2711 +2695 @@
 
 \begin{table}
-\centering
 \caption{Properties of benchmark code}
 \label{tab:eval}
+\centering
 \newcommand{\CT}[1]{\multicolumn{1}{c}{#1}}
 \begin{tabular}{rrrrr}
@@ -2726 +2710 @@
 The C and \CCV variants are generally the slowest with the largest memory footprint, because of their less-efficient memory layout and the pointer-indirection necessary to implement generic types;
 this inefficiency is exacerbated by the second level of generic types in the pair benchmarks.
-By contrast, the \CFA and \CC variants run in roughly equivalent time for both the integer and pair of @short@ and @char@ because the storage layout is equivalent, with the inlined libraries (\ie no separate compilation) and greater maturity of the \CC compiler contributing to its lead.
+By contrast, the \CFA and \CC variants run in roughly equivalent time for both the integer and pair because of equivalent storage layout, with the inlined libraries (\ie no separate compilation) and greater maturity of the \CC compiler contributing to its lead.
 \CCV is slower than C largely due to the cost of runtime type-checking of down-casts (implemented with @dynamic_cast@);
-The outlier in the graph for \CFA, pop @pair@, results from the complexity of the generated-C polymorphic code.
-The gcc compiler is unable to optimize some dead code and condense nested calls; a compiler designed for \CFA could easily perform these optimizations.
+The outlier for \CFA, pop @pair@, results from the complexity of the generated-C polymorphic code.
+The gcc compiler is unable to optimize some dead code and condense nested calls;
+a compiler designed for \CFA could easily perform these optimizations.
 Finally, the binary size for \CFA is larger because of static linking with the \CFA libraries.
 
@@ -2746 +2731 @@
 The \CFA benchmark is able to eliminate all redundant type annotations through use of the polymorphic @alloc@ function discussed in Section~\ref{sec:libraries}.
 
+We conjecture these results scale across most generic data-types as the underlying polymorphic implement is constant.
+
 
 \section{Related Work}
@@ -2751 +2738 @@
 
 \subsection{Polymorphism}
+
+ML~\cite{ML} was the first language to support parametric polymorphism.
+Like \CFA, it supports universal type parameters, but not the use of assertions and traits to constrain type arguments.
+Haskell~\cite{Haskell10} combines ML-style polymorphism, polymorphic data types, and type inference with the notion of type classes, collections of overloadable methods that correspond in intent to traits in \CFA.
+Unlike \CFA, Haskell requires an explicit association between types and their classes that specifies the implementation of operations.
+These associations determine the functions that are assertion arguments for particular combinations of class and type, in contrast to \CFA where the assertion arguments are selected at function call sites based upon the set of operations in scope at that point.
+Haskell also severely restricts the use of overloading: an overloaded name can only be associated with a single class, and methods with overloaded names can only be defined as part of instance declarations.
 
 \CC provides three disjoint polymorphic extensions to C: overloading, inheritance, and templates.
@@ -2804 +2798 @@
 Go does not have tuples but supports MRVF.
 Java's variadic functions appear similar to C's but are type-safe using homogeneous arrays, which are less useful than \CFA's heterogeneously-typed variadic functions.
-Tuples are a fundamental abstraction in most functional programming languages, such as Standard ML~\cite{sml} and~\cite{Scala}, which decompose tuples using pattern matching.
+Tuples are a fundamental abstraction in most functional programming languages, such as Standard ML~\cite{sml}, Haskell, and Scala~\cite{Scala}, which decompose tuples using pattern matching.
 
 
@@ -2835 +2829 @@
 Finally, we demonstrate that \CFA performance for some idiomatic cases is better than C and close to \CC, showing the design is practically applicable.
 
-There is ongoing work on a wide range of \CFA features, including arrays with size, runtime type-information, virtual functions, user-defined conversions, concurrent primitives, and modules.
-While all examples in the paper compile and run, a public beta-release of \CFA will take another 8--12 months to finalize these extensions.
-There are also interesting future directions for the polymorphism design.
-Notably, \CC template functions trade compile time and code bloat for optimal runtime of individual instantiations of polymorphic functions.
-\CFA polymorphic functions use dynamic virtual-dispatch;
-the runtime overhead of this approach is low, but not as low as inlining, and it may be beneficial to provide a mechanism for performance-sensitive code.
+While all examples in the paper compile and run, a public beta-release of \CFA will take 6--8 months to reduce compilation time, provide better debugging, and add a few more libraries.
+There is also new work on a number of \CFA features, including arrays with size, runtime type-information, virtual functions, user-defined conversions, and modules.
+While \CFA polymorphic functions use dynamic virtual-dispatch with low runtime overhead (see Section~\ref{sec:eval}), it is not as low as \CC template-inlining.
+Hence it may be beneficial to provide a mechanism for performance-sensitive code.
 Two promising approaches are an @inline@ annotation at polymorphic function call sites to create a template-specialization of the function (provided the code is visible) or placing an @inline@ annotation on polymorphic function-definitions to instantiate a specialized version for some set of types (\CC template specialization).
 These approaches are not mutually exclusive and allow performance optimizations to be applied only when necessary, without suffering global code-bloat.
@@ -2849 +2841 @@
 
 The authors would like to recognize the design assistance of Glen Ditchfield, Richard Bilson, Thierry Delisle, Andrew Beach and Brice Dobry on the features described in this paper, and thank Magnus Madsen for feedback on the writing.
-This work is supported by a corporate partnership with Huawei Ltd.\ (\url{http://www.huawei.com}), and Aaron Moss and Peter Buhr are partially funded by the Natural Sciences and Engineering Research Council of Canada.
-
-
+Funding for this project has been provided by Huawei Ltd.\ (\url{http://www.huawei.com}), and Aaron Moss and Peter Buhr are partially funded by the Natural Sciences and Engineering Research Council of Canada.
+
+{%
+\fontsize{9bp}{12bp}\selectfont%
 \bibliography{pl}
-
+}%
 
 \appendix

doc/papers/general/evaluation/timing.gp

@@ -25 +25 @@
 
 set label "23.9" at 7.125,10.5
-
+set style fill pattern 4 border lt -1
 # set datafile separator ","
 plot for [COL=2:5] 'evaluation/timing.dat' using (column(COL)/SCALE):xticlabels(1) title columnheader