Context Navigation

-              rfe6047c
+              r67748f9
     void f( int n, float[][n]  );   $\C{// array of VLAs}$
 \end{cfa}
 as a repeat, without an error about conflicting types for @f@.
 Yet, entirely different stride calculations would occur in a function body whose parameters were declared in each of the two styles.
+without an error about conflicting types for @f@.
+Yet, entirely different stride calculations occur in the function body for each of the two parameter styles.
 \begin{figure}
 …
 \subsection{Arrays Could be Values}
+\label{s:ArraysCouldbeValues}
 All arrays have a know runtime size at their point of declaration.

doc/theses/mike_brooks_MMath/uw-ethesis-frontpgs.tex

rfe6047c	r67748f9
139	139	Often, the array is part of the programming language, while linked lists are built from (recursive) pointer types, and strings from arrays and/or linked lists.
140	140	For all three types, languages and/or their libraries supply varying degrees of high-level mechanisms for manipulating these objects at the bulk and component levels, such as copying, slicing, extracting, and iterating among elements.
141		Unfortunately, typical solutions for the the ~~key types in C cause 60\%--70\% of the reported software vulnerabilities involving memory errors; 70\%--80\% of hacker attack~~ vectors target these types.
	141	Unfortunately, typical solutions for the these key types in C cause 60\%--70\% of the reported software vulnerabilities involving memory errors; 70\%--80\% of hacker attack-vectors target these types.
142	142	Therefore, hardening these three C types goes a long way to make the majority of C programs safer.
143	143

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