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: Stephen Leake Subject: Re: Naming of Tagged Types and Associated Packages Date: 1998/07/28 Message-ID: #1/1 X-Deja-AN: 375707053 References: <6pdhfo$1br$1@platane.wanadoo.fr> <6pi0pf$df8$1@nnrp1.dejanews.com> <6pirk1$iar$1@nnrp1.dejanews.com> <6pknto$163a$1@mdnews.btv.ibm.com> Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA Newsgroups: comp.lang.ada Date: 1998-07-28T00:00:00+00:00 List-Id: "Norman H. Cohen" writes: > dennison@telepath.com wrote in message <6pirk1$iar$1@nnrp1.dejanews.com>... > > >Again, you have encoded the fact that it is a type in the type's name. I > don't > >need that information, and it leads to really stupid looking things like > >"Command_Type_Type". > > > Consider Command_Variant_Type, or Command_Format_Type, or Command_Kind_Type. > > The _Type suffix serves not only to announce "This is a type name," but to > leave other parts of the name space available for other purposes, e.g. for a > variable or formal parameter named Command_Kind, of type Command_Kind_Type. I'll go with Ted Dennison here, partly. I use _Type, and I often run into hardware descriptions of the form "register x bits 1 .. 3 store the command type", so the natural name for this object's type is Command_Type_Type. I usually change the name to Command_Label_Type; I'm more commited to _Type than to matching the hardware documentation. That is bolstered by the fact that I have yet to find a hardware manual with a clear, consistent naming convention, so I don't mind "fixing" it. -- Stephe