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: dennison@telepath.com
Subject: Re: Naming of Tagged Types and Associated Packages
Date: 1998/07/30
Message-ID: <6pqeq2$imm$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 376402135
References: <ur9zlv6tx.fsf@sandia.SPAMFREE.gov>
 <m34sw6mcbx.fsf@mheaney.ni.net> <6pdhfo$1br$1@platane.wanadoo.fr>
 <m367gl943o.fsf@mheaney.ni.net> <6pi0pf$df8$1@nnrp1.dejanews.com>
 <uogub2jq5.fsf@gsfc.nasa.gov> <6pirk1$iar$1@nnrp1.dejanews.com>
 <Pine.BSF.3.96.980727153418.13706B-100000@shell5.ba.best.com>
 <6pknai$qst$1@nnrp1.dejanews.com>
 <Pine.BSF.3.96.980728084100.28778A-100000@shell5.ba.best.com>
 <6pl5rh$elr$1@nnrp1.dejanews.com> <m33eblyg8t.fsf@mheaney.ni.net>
 <35BF50B4.6FDCDDA0@west.raytheon.com> <m3vhogw00r.fsf@mheaney.ni.net>
 <6pq2ck$1pi$1@nnrp1.dejanews.com> <m3pvenww5v.fsf@mheaney.ni.net>
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Thu Jul 30 18:42:10 1998 GMT
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.0; Windows NT; Gateway2000)
Date: 1998-07-30T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <m3pvenww5v.fsf@mheaney.ni.net>,
  Matthew Heaney <matthew_heaney@acm.org> wrote:
> dennison@telepath.com writes:
>
> > I still whould have gone with "File" instead of "File_Type".
> > :-)
>
> I'm not sure why there's a smiley there, but in general, types should be
> named using a two-part phrase.  That way you can name the object using a
> shortened version of the type name, as in

The smiley was there because this is clearly a matter of taste. The rule I
live by is that objects (including types) should be named as specific to the
role they serve as is reasonable. Couple that with full dot notation and name
clashes really are rather rare. For instance your declaration for file
becomes:

  File : Configuration_IO.File;

or better yet, something like:

  Configuration_File : Configuration_IO.File;

...but that's me.

T.E.D.

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum