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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,dfe340a115a0bc1 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-02-04 00:06:36 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!attbi_feed3!attbi.com!attbi_s03.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Naming convention for classes? References: X-Newsreader: Tom's custom newsreader Message-ID: NNTP-Posting-Host: 67.161.24.134 X-Complaints-To: abuse@comcast.net X-Trace: attbi_s03 1075881995 67.161.24.134 (Wed, 04 Feb 2004 08:06:35 GMT) NNTP-Posting-Date: Wed, 04 Feb 2004 08:06:35 GMT Organization: Comcast Online Date: Wed, 04 Feb 2004 08:06:35 GMT Xref: archiver1.google.com comp.lang.ada:5212 Date: 2004-02-04T08:06:35+00:00 List-Id: > Today : Date.Object; > Today : Date; >The second approach seems natural ... Agreed. Remember that a package can contain more than one type definition, and in general a package is a higher level of abstraction than any one of its contents. So you might do package Timestamps is type Date is ... or package Historical_Records is type Date is ... But as noted, it's often not obvious and it comes down to a personal stylistic preference - presumably a reasonably consistent one. Have you looked at "Ada Quality and Style"?