DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400 Tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400 Tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download
Index: ┃ T V

⟦5d05f7980⟧ TextFile

    Length: 2758 (0xac6)
    Types: TextFile
    Names: »V«

Derivation

└─⟦149519bd4⟧ Bits:30000546 8mm tape, Rational 1000, !projects 93-07-13
    └─ ⟦124ff5788⟧ »DATA« 
        └─⟦this⟧ 
└─⟦f64eaa120⟧ Bits:30000752 8mm tape, Rational 1000, !projects 93 02 16
    └─ ⟦6f12a12be⟧ »DATA« 
        └─⟦this⟧ 

TextFile

WITH Interchange;
WITH Rpc;
WITH Transport_Defs;
PACKAGE Complex_Defs IS


   TYPE Number IS
      RECORD
         Real, Imag : Float;
      END RECORD;

   GENERIC
      TYPE Stream_Id IS LIMITED PRIVATE;
      WITH PROCEDURE Put (Into : Stream_Id; Data : Interchange.Float) IS <>;
      WITH PROCEDURE Get (From :     Stream_Id;
                          Data : OUT Interchange.Float)               IS <>;
   PACKAGE Interchange_Operations IS
      PROCEDURE Put (Into : Stream_Id; Data : Number);
      PROCEDURE Get (From : Stream_Id; Data : OUT Number);  
   END Interchange_Operations;

   FUNCTION Network RETURN Transport_Defs.Network_Name;
   -- The constant Network was replaced with this function so that the actual
   -- network name value could be embedded in the body and reduce compilation
   -- dependencies...LP
   --


   -- The two functions below Sparc_Socket and R1000_Socket return the
   -- values to be used by the Server task when it is run from the Sparc
   -- station or R1000, respectively.
   --
   -- The client task will use the correct socket value to communicate with
   -- the Server.  For instance, if the Server is running on the R1000 then
   -- the client task would also use R1000_Socket.  If however, the Server
   -- is running on the Sparc_Station, it would use Sparc_Socket.
   --
   -- Function calls are used so that the actual socket values are embedded
   -- in the package body to minimize recompilation dependencies should the
   -- socket values require changing.

   FUNCTION Sparc_Socket RETURN Transport_Defs.Socket_Id;
   -- This function returns the socket value to be used by the Server when
   -- run on the workstation.


   FUNCTION R1000_Socket RETURN Transport_Defs.Socket_Id;
   -- This function returns the socket value to be used by the Server when
   -- run on the R1000.



   -- The constant Socket was replaced with this function so that the actual
   -- socket value could be embedded in the body and reduce compilation
   -- dependencies...LP
   --

   Program : CONSTANT Rpc.Program_Number := 45;
   Version : CONSTANT Rpc.Version_Number := 0;

   PACKAGE Proc_Number IS
      Make           : CONSTANT Rpc.Procedure_Number := 0;
      Real_Part      : CONSTANT Rpc.Procedure_Number := 1;
      Imaginary_Part : CONSTANT Rpc.Procedure_Number := 2;
      Plus           : CONSTANT Rpc.Procedure_Number := 3;
      Minus          : CONSTANT Rpc.Procedure_Number := 4;
      Image          : CONSTANT Rpc.Procedure_Number := 5;
      Value          : CONSTANT Rpc.Procedure_Number := 6;
   END Proc_Number;

   PACKAGE Exception_Number IS
      Overflow  : CONSTANT Rpc.Exception_Number := 1;
      Underflow : CONSTANT Rpc.Exception_Number := 2;
   END Exception_Number;

END Complex_Defs;