DataMuseum.dk

top - metrics - download

    Length: 4138 (0x102a)
    Types: TextFile
    Names: »V«

└─⟦5f3412b64⟧ Bits:30000745 8mm tape, Rational 1000, ENVIRONMENT 12_6_5 TOOLS 
    └─⟦91c658230⟧ »DATA« 
        └─⟦458657fb6⟧ 
            └─⟦a5bbbb819⟧ 
                └─⟦this⟧ 
└─⟦d10a02448⟧ Bits:30000409 8mm tape, Rational 1000, ENVIRONMENT, D_12_7_3
    └─⟦fc9b38f02⟧ »DATA« 
        └─⟦9b46a407a⟧ 
            └─⟦eec0a994f⟧ 
                └─⟦this⟧ 

TextFile

package Check is

    -- Check that units in a load view are compatible with the
    -- corresponding units in a spec view.  A unit in a load view
    -- is compatible with a spec view unit if every declaration
    -- exported by the spec view unit is also exported by the
    -- load view unit.  The declarations need not be in the same
    -- order in the two units nor do they need to be textually
    -- identical (two declarations are considered equaivalent
    -- if they match according to the subprogram specification
    -- conformance rules of LRM 6.3.1).  In addition, units
    -- must be (at least) installed and reside in worlds with
    -- compatible target keys.  For units in the coded state,
    -- a check is made that they were coded using compatible
    -- versions of the code generator.

    type Status is (Compatible, Incompatible, Error);


    procedure Units (Load_View_Units : String  := "<CURSOR>";
                     Spec_Views      : String  := "<ACTIVITY>";
                     Menu            : Boolean := False;
                     Response        : String  := "<PROFILE>");

    function Units (Load_View_Units : String := "<CURSOR>";
                    Spec_Views      : String := "<ACTIVITY>";
                    Response        : String := "<PROFILE>") return Status;

    -- For each load view unit, check its compatibility with its
    -- corresponding spec view unit.  The set of corresponding
    -- spec views may be given explicitly using a naming expression
    -- that resolves to a set of views, or may be given implicitly
    -- as a set of spec views in some activity.  In either case,
    -- there must be exactly one spec view for each load view.

    -- The results of the compatibility check may be reported
    -- in the log file or as a menu of the spec view units that
    -- were incompatible with their corresponding load view units.
    -- When a unit on the menu is visited, the incompatible
    -- declarations will be underlined.


    procedure Views (Load_Views : String  := "<CURSOR>";
                     Spec_Views : String  := "<ACTIVITY>";
                     Menu       : Boolean := False;
                     Response   : String  := "<PROFILE>");

    function Views (Load_Views : String := "<CURSOR>";
                    Spec_Views : String := "<ACTIVITY>";
                    Response   : String := "<PROFILE>") return Status;

    -- For each load view, find the corresponding spec view and
    -- check all of the exported ada specs for compatibility.
    -- The set of corresponding spec views may be given explicitly
    -- using a naming expression that resolves to a set of views,
    -- or may be given implicitly as the set of spec views in some
    -- activity.  In either case, there must be exactly one spec
    -- view for each load view.


    procedure Activity (The_Activity : String  := "<ACTIVITY>";
                        Menu         : Boolean := False;
                        Response     : String  := "<PROFILE>");

    function Activity (The_Activity : String := "<ACTIVITY>";
                       Response     : String := "<PROFILE>") return Status;

    -- Check that each spec view in the specified activity is
    -- compatible with its corresponding load view.

    procedure Code_Views (Code_Views : String := "<CURSOR>";
                          Response   : String := "<PROFILE>");

    function Code_Views (Code_Views : String := "<CURSOR>";
                         Response   : String := "<PROFILE>") return Status;

    -- For each code view, check that each spec view unit referenced
    -- when the code view was created still exists and still exports
    -- the entities used by the code view.  The naming expression specifying
    -- the Code_Views may resolve to any type of view.  Those that are
    -- not actually code views will be ignored.  In particular,
    -- Code_Views may be specified indirectly by an activity, in which
    -- case all code views referenced by that activity will be checked.

    -- The results of the code view compatibility check are reported
    -- in the log file.

end Check;