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: Matthew Heaney Subject: Re: Naming of Tagged Types and Associated Packages Date: 1998/07/29 Message-ID: #1/1 X-Deja-AN: 375924642 Sender: matt@mheaney.ni.net References: <6pdhfo$1br$1@platane.wanadoo.fr> <6pi0pf$df8$1@nnrp1.dejanews.com> <6pirk1$iar$1@nnrp1.dejanews.com> <6pknai$qst$1@nnrp1.dejanews.com> NNTP-Posting-Date: Wed, 29 Jul 1998 00:35:39 PDT Newsgroups: comp.lang.ada Date: 1998-07-29T00:00:00+00:00 List-Id: Brian Rogoff writes: > On Tue, 28 Jul 1998, Brian Rogoff wrote: > > My issue with this is that I often coencapsulate types, and sometimes > > there is no main type in a package, though I suppose thats easy enough to > > fix by using T,U,V,W, ... or T1, T2, T3, ... > > Oops, I forgot to put a string of ":-)" here! But you bring up a good point. Frequently, there are types that are cohesive enough that they really belong together in the same package. An example is a data structure (say a stack or queue) and its associated active iterator, connected by a factory method. The problem is, if you name the stack type Instance, then what do you name the iterator type?