[BACK]Return to openxm-stackmachines.tex CVS log [TXT][DIR] Up to [local] / OpenXM / doc / issac2000

Diff for /OpenXM/doc/issac2000/openxm-stackmachines.tex between version 1.7 and 1.8

version 1.7, 2000/01/14 10:45:10 version 1.8, 2000/01/15 03:46:27
Line 1 
Line 1 
 % $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.6 2000/01/13 10:54:33 ohara Exp $  % $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.7 2000/01/14 10:45:10 tam Exp $
   
 \section{OpenXM Stack machines}\label{sec:ox-stackmachines} (Tamura)  \section{OpenXM Stack machines}\label{sec:ox-stackmachines} (Tamura)
   
 In OpenXM specification, all servers are stack machines.  In OpenXM specification, all servers are stack machines.
 These are called OpenXM stack machines.  %These are called OpenXM stack machines.
 When a server ox\_xyz gets an OX data message,  When a server ox\_xyz gets an OX data message,
 it translates the data into an object of its local mathematical system  it translates the data into an object of its local mathematical system
 and push the object on the stack.  and push the object on the stack.
 The translation scheme together with definitions of mathematical operations  Following the OpenMath specification,
 of the system ox\_xyz is called the {\it PhraseBook} of  the translation scheme together with definitions of mathematical operations
 ox\_xyz following the OpenMath specification.  of the system ox\_xyz is called the {\it PhraseBook} of ox\_xyz.
   
 Any OX command message starts with the int32 tag OX\_COMMAND.  Any OX command message starts with the int32 tag OX\_COMMAND.
 The body is OpenXM stack machine operation code expressed by int32.  The body is an OpenXM stack machine operation code expressed by int32.
 The codes are listed below.  The codes are listed below.
 \begin{verbatim}  \begin{verbatim}
 #define SM_popSerializedLocalObject               258  #define SM_popSerializedLocalObject               258
Line 41  The codes are listed below.
Line 41  The codes are listed below.
   
 OpenXM does not have a standard for mathematical operation sets  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 \cite{gap}.
 Each OpenXM server has its own mathematical operation set.  Each OpenXM server has its own set of mathematical operations,
 Mathematical operations are performed as follows.  which are performed as follows.
 Mathematical operator name, such as fctr (asir factorization command),  Mathematical operator name, such as {\tt fctr} (asir factorization command),
 is pushed as a string,  is pushed as a string,
 the stack machine command  the stack machine command
 SM\_executeFunction (269) pops the operator name, the number of arguments  {\tt SM\_executeFunction} (269) pops the operator name, the number of arguments
 and arguments, and  and arguments, and
 the OX stack machine evaluates the operator, and pushes the result on the stack.  the OX stack machine evaluates the operator, and pushes the result onto the stack.
 For example, the following code factorizes $x^{100}-1$ by calling  For example, the following code factorizes $x^{100}-1$ by calling
 ox\_asir from asir.  ox\_asir from asir.
 \begin{verbatim}  \begin{verbatim}
 P = ox_launch();  P = ox_launch();
 ox_push_cmo(P,x^100-1); ox_push_cmo(P,ox_int32(1));  ox_push_cmo(P,x^100-1); ox_push_cmo(P,ntoint32(1));
 ox_push_cmd(P,269);  ox_push_cmd(P,269);
 Ans = ox_pop_cmo(P);  Ans = ox_pop_cmo(P);
 \end{verbatim}  \end{verbatim}
Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>