Changeset 08061589 for doc/user

Timestamp:

Jul 31, 2016, 7:06:22 PM (9 years ago)

Author:

Peter A. Buhr <pabuhr@…>

Branches:

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

Children:

182fe1e

Parents:

057b34f

Message:

more case statement cleanup

File:

• doc/user/user.tex (modified) (4 diffs)

doc/user/user.tex

@@ -10 +10 @@
 %% Author           : Peter A. Buhr
 %% Created On       : Wed Apr  6 14:53:29 2016
-%% Last Modified By : Peter A. Buhr
-%% Last Modified On : Wed Jul 13 08:14:39 2016
-%% Update Count     : 1247
+%% Last Modified By : 
+%% Last Modified On : Sun Jul 31 07:27:55 2016
+%% Update Count     : 1254
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
@@ -1778 +1778 @@
 and there is only a medium amount of fall-through from one ©case© clause to the next, and most of these result from a list of case values executing common code, rather than a sequence of case actions that compound.
 \end{itemize}
-These observations help to put the suggested changes to the ©switch© into perspective.
+These observations help to put the \CFA changes to the ©switch© into perspective.
 \begin{enumerate}
 \item
@@ -1788 +1788 @@
 still work.
 Nevertheless, reversing the default action would have a non-trivial effect on case actions that compound, such as the above example of processing shell arguments.
-Therefore, to preserve backwards compatibility, it is necessary to introduce a new kind of ©switch© statement, called ©choose©, with no implicit fall-through semantics and an explicit fall-through if the last statement of a case-clause ends with the new keyword ©fallthru©, e.g.:
+Therefore, to preserve backwards compatibility, it is necessary to introduce a new kind of ©switch© statement, called ©choose©, with no implicit fall-through semantics and an explicit fall-through if the last statement of a case-clause ends with the new keyword ©fallthrough©/©fallthru©, e.g.:
 \begin{lstlisting}
 ®choose® ( i ) {
@@ -4342 +4342 @@
 
 
+\section{New Keywowrds}
+
+©catch©, ©catchResume©, ©choose©, \quad ©disable©, ©dtype©, \quad ©enable©, \quad ©fallthrough©, ©fallthru©, ©finally©, ©forall©, ©ftype©, \quad ©lvalue©, \quad ©otype©, \quad ©throw©, ©throwResume©, ©trait©, ©try©
+
+
 \section{Incompatible}