From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,63a41ccea0fc803a
X-Google-Attributes: gid103376,public
From: stt@houdini.camb.inmet.com (Tucker Taft)
Subject: Re: Naming of Tagged Types and Associated Packages
Date: 1998/08/06
Message-ID: <Ex9unC.43p.0.-s@inmet.camb.inmet.com>#1/1
X-Deja-AN: 378524371
Sender: news@inmet.camb.inmet.com (USENET news)
X-Nntp-Posting-Host: houdini.camb.inmet.com
References: <m3af5jm7fy.fsf@mheaney.ni.net>
Organization: Intermetrics, Inc.
Newsgroups: comp.lang.ada
Date: 1998-08-06T00:00:00+00:00
List-Id: <comp.lang.ada>

We have been quite happy for the past 15 years (and > 1M SLOC)
using the with/rename approach, exemplified by:

with Ada.Strings.Bounded;
  ...
    package ASB renames Ada.Strings.Bounded;
  ...

    X : ASB.Bounded_String;

  ...

    if ASB.Length(X) = 0 then ...

This makes it very easy to follow all references, without 
overwhelming the user with repetitive, long-winded package
names everywhere.  All of the package renames are at the
beginning of the compilation unit containing the references.
Ideally, the abbreviations are agreed-upon on a project-wide basis.

For primitive operators (presuming they have their "intuitive" meaning ;-), 
I would certainly recommend "use type", but given the above approach, 
there is almost never a need for "use"ing a package.
    
--
-Tucker Taft   stt@inmet.com   http://www.inmet.com/~stt/
Intermetrics, Inc.  Burlington, MA  USA
An AverStar company.