[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.4 and 1.5

version 1.4, 2000/01/07 09:56:08 version 1.5, 2000/01/07 10:22:41
Line 1 
Line 1 
 % $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.3 2000/01/03 04:27:52 takayama Exp $  % $OpenXM: OpenXM/doc/issac2000/openxm-stackmachines.tex,v 1.4 2000/01/07 09:56:08 ohara Exp $
   
 \section{OpenXM Stack machines}   (Tamura)  \section{OpenXM Stack machines}   (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 its own object and push the object  it translates the data into an object of its local mathematical system
 on the stack.  and push the object on the stack.
 The translation scheme together with definitions of  The translation scheme together with definitions of
 mathematical operations  mathematical operations
 of the system ox\_xyz is called the {\it phrase dictionary} of  of the system ox\_xyz is called the {\it PhraseBook} of
 ox\_xyz following the OpenMath specification.  ox\_xyz following the OpenMath specification.
   
 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 OX stack machine operation code expressed by int32.  The body is 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
Legend:
Removed from v.1.4  
changed lines
  Added in v.1.5
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>