===================================================================
RCS file: /home/cvs/OpenXM/doc/issac2000/openxm-stackmachines.tex,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -p -r1.8 -r1.9
--- OpenXM/doc/issac2000/openxm-stackmachines.tex	2000/01/15 03:46:27	1.8
+++ OpenXM/doc/issac2000/openxm-stackmachines.tex	2000/01/15 12:18:42	1.9
@@ -1,13 +1,13 @@
-% $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.7 2000/01/14 10:45:10 tam Exp $
+% $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.8 2000/01/15 03:46:27 noro Exp $
 
-\section{OpenXM Stack machines}\label{sec:ox-stackmachines} (Tamura)
+\section{OpenXM Stack machines}\label{sec:ox-stackmachines}
 
 In OpenXM specification, all servers are stack machines.
 %These are called OpenXM stack machines.
 When a server ox\_xyz gets an OX data message,
-it translates the data into an object of its local mathematical system 
-and push the object on the stack.
-Following the OpenMath specification, 
+it translates the data into a local object of ox\_xyz
+and pushes the object onto the stack.
+According to the OpenMath specification, 
 the translation scheme together with definitions of mathematical operations
 of the system ox\_xyz is called the {\it PhraseBook} of ox\_xyz.
 
@@ -31,8 +31,6 @@ The codes are listed below.
 #define SM_executeStringByLocalParserInBatchMode  274
 #define SM_getsp                                  275
 #define SM_dupErrors                              276
-#define SM_DUMMY_sendcmo                          280
-#define SM_sync_ball                              281
 #define SM_control_kill                          1024
 #define SM_control_to_debug_mode                 1025
 #define SM_control_exit_debug_mode               1026
@@ -40,17 +38,22 @@ The codes are listed below.
 \end{verbatim}
 
 OpenXM does not have a standard for mathematical operation sets
-while it is a work in progress in \cite{gap}.
+while it is a work in progress in the GAP group \cite{gap}.
 Each OpenXM server has its own set of mathematical operations,
 which are performed as follows.
-Mathematical operator name, such as {\tt fctr} (asir factorization command),
-is pushed as a string,
-the stack machine command
-{\tt SM\_executeFunction} (269) pops the operator name, the number of arguments
-and arguments, and
-the OX stack machine evaluates the operator, and pushes the result onto the stack.
+First, arguments for a mathematical operation
+and the number of the arguments are pushed.
+Second, 
+the mathematical operator name, 
+such as {\tt fctr} (asir factorization command),
+is pushed as a string.
+Finally, the stack machine command
+{\tt SM\_executeFunction} (269) evaluates the operator and
+pushes the result onto the stack
+after poping the operator name, the number of arguments
+and arguments.
 For example, the following code factorizes $x^{100}-1$ by calling
-ox\_asir from asir.
+{\tt ox\_asir} from asir.
 \begin{verbatim}
 P = ox_launch(); 
 ox_push_cmo(P,x^100-1); ox_push_cmo(P,ntoint32(1));
@@ -69,10 +72,10 @@ error([8,fctr : invalid argument])
 \end{verbatim}
 
 OpenXM server won't send error messages to the client
-except when it receives a SM\_pop* command.
-OX stackmachines works in the asynchronous mode which is similar 
+except when it receives a {\tt SM\_pop*} command.
+OX stackmachines work in the asynchronous mode which is similar 
 to X servers.
-For servers for graphic applications, it is an advantageous feature.
+For servers for graphic and sound applications, it is an advantageous feature.
 It is also easy to emulate RPC and a web server for MCP \cite{iamc} 
 on our asynchronous OX stackmachines.