From fc94039576cdf10ea5b8b2535aae01fdef42919f Mon Sep 17 00:00:00 2001 From: Geoffrey Challen Date: Tue, 23 Dec 2014 12:42:49 -0500 Subject: [PATCH] New. --- certainty.tex | 18 +++++++++--------- maybe.tex | 2 +- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/certainty.tex b/certainty.tex index f9d8bfb..2fc27b7 100644 --- a/certainty.tex +++ b/certainty.tex @@ -112,20 +112,20 @@ only change when the developer expects them to. \subsubsection{Simulation or emulation} Pre-deployment simulation or emulation may provide a way to efficiently -assess \texttt{maybe} statements without involving users. Building simulation -environments that accurately reflect all of the uncertainties inherent to -mobile systems programming, however, is difficult. To complicate matters, -\texttt{maybe} alternatives may depend on details of user interaction that -are difficult to know \textit{a priori}, particularly when new apps or -functionalities are being investigated. So in most cases we believe -post-deployment testing will be required. +evaluate \texttt{maybe} statements without involving users. Building +simulation environments that accurately reflect all of the uncertainties +inherent to mobile systems programming, however, is difficult. To complicate +matters, \texttt{maybe} alternatives may depend on details of user +interaction that are difficult to know \textit{a priori}, particularly when +new apps or functionalities are being investigated. So in most cases we +believe post-deployment testing will be required. However, pre-deployment testing may still be a valuable approach, particularly when a large number of \texttt{maybe} statements are being used. Since this can explode the adaptation space, simulations may be able to help guide the developer's choices of which \texttt{maybe} statements may have a -significant impact on performance and should be assessed first. Other -\texttt{maybe} statements can be assessed later or eliminated. +significant impact on performance and should be evaluated first. Other +\texttt{maybe} statements can be evaluated later or eliminated. \subsubsection{Split testing} diff --git a/maybe.tex b/maybe.tex index 7bebf90..10245b0 100644 --- a/maybe.tex +++ b/maybe.tex @@ -66,7 +66,7 @@ Figure~\ref{fig-maybeexamples} shows several extensions of the \texttt{maybe} statement providing syntactic sugar. \texttt{maybe} function annotations allow uncertainty to be expressed at the function level, with the alternatives consisting of multiple function definitions with identical -signatures. Finally, \texttt{maybe} blocks that require custom evaluation +signatures. Finally, \texttt{maybe} statements that require custom evaluation logic can include an \texttt{evaluate} block as shown in the final example. \texttt{evaluate} blocks provide app-specific \textit{a posteriori} logic to evaluate the selected alternative. The \texttt{evaluate} block must return a -- libgit2 0.22.2