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

⟦e2f832e54⟧ TextFile

    Length: 2761 (0xac9)
    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;