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 - metrics - download
Index: T V

⟦10c0f8cf1⟧ TextFile

    Length: 1329 (0x531)
    Types: TextFile
    Names: »V«

Derivation

└─⟦180fe333a⟧ Bits:30000405 8mm tape, Rational 1000, SW CATALOG, 10_20_0
└─⟦180fe333a⟧ Bits:30000537 8mm tape, Rational 1000, SW Catalog 10_20_0
    └─⟦5cb1d1d7f⟧ »DATA« 
        └─⟦3b1ee7bd8⟧ 
            └─⟦this⟧ 

TextFile

-- Rational has found that certain customers required the image of an
-- Ada unit to be different than Rational's current pretty printer output.
-- In particular, one customer required that "then" keywords of an
-- if statement appear on the next line of the output and be aligned with
-- the if keyword.  For example:
--
--       Instead of:
--
--           if [conditional expression] then
--               [statement]
--           elsif [conditional expression] then
--               [statement]
--           end if;
--
--       They Required:
--
--           if [conditional expression]
--           then
--               [statement]
--           elsif [conditional expression]
--           then
--               [statement]
--           end if;
--
--  They following procedure should take input from an Ada Unit in the form
--  that Rational's pretty printer current generates and create a new
--  file with the alteranative format.
--
--  Some things to watch out for:
--
--     1)  The then can already be on the next line if the user put
--         a line break after the conditional expression.
--
--     2)  Comments can contain the keywords "if" and "then"
--
--     3)  There are many other cases.  See how many of them you
--         can find.
--
procedure Format (Input_Filename : String; Output_Filename : String);