RE: Ada95 tutorials with sample code.

["Robert C. Leif, Ph.D." <rleif@rleif.com>]

From: Bob Leif
To: Sven Nilsson et al.

In general, I agree that the excessive Use clauses can be a real pain when
it comes to understanding or maintaining Ada source.
I have suggested that a Table of Contents comment (annotation) before the
package renames section and an End Table of Contents afterwards would be a
much better way to communicate. I would also like and would pay a reasonable
price for a an ASIS tool that undid the Use clauses. It  could be named
Pragma No_Use.

-----Original Message-----
From: comp.lang.ada-admin@ada.eu.org
[mailto:comp.lang.ada-admin@ada.eu.org]On Behalf Of Sven Nilsson
Sent: Monday, March 05, 2001 11:13 PM
To: comp.lang.ada@ada.eu.org
Subject: Re: Ada95 tutorials with sample code.


I'm sorry if I disrupt this thread with a slightly off-topic question
(which I'm sure has been discussed countless times before) BUT

This use-thingy. Is it really ant good? I've only ever used Ada in HUGE
projects with loads of people writing the code and I've found that the
use-clause can be a real pain as it dosn't give you a clue as to where
things are declared. Right now I'm teaching new arrivals about Ada 95
and I invariably tell them NOT to use the use-clause.
Now, there're a lot of very clever and skilled people reading this
news-group and I'd be interested in your feelings on "use". Is it a Do
or Don't? Generally speaking?

My Hello World would probably look something like this:

-- "Hello, World"

with Ada.Text_IO;

procedure Hello_World is
package Tio renames Ada.Text_IO; -- Rename common packages so I don't
have to
                                 -- type in the whole thing every time I
use it
begin
   Tio.Put_Line("Howdy, World!"); -- Use Tio to access Ada.Text_IO
end Hello_World;

> -- "Hello, World!" program in Ada
>
> with Ada.Text_IO;
>
> use Ada.Text_IO;
> procedure Hello_World is
>    -- null;
> begin -- Hello_World
>    Put_Line (Item => "Hello, World!");
> end Hello_World;
>

-Sven