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,2078dddcdcd8d83 X-Google-Attributes: gid103376,public From: kaz@vision.crest.nt.com (Kaz Kylheku) Subject: Re: Warning: Religious naming convention discussion :-) [was: assign help!!] Date: 1997/05/10 Message-ID: <5l0vff$8hn@bcrkh13.bnr.ca>#1/1 X-Deja-AN: 240447984 References: <5kjvcv$evt@news.cis.nctu.edu.tw> <5kuf1j$17vi@uni.library.ucla.edu> <3373666A.31DFF4F5@spam.innocon.com> <3373EAB5.73A0@sprintmail.com> Organization: Prism Systems Inc. Newsgroups: comp.lang.ada Date: 1997-05-10T00:00:00+00:00 List-Id: In article <3373EAB5.73A0@sprintmail.com>, John G. Volan wrote: >Jeff Carter wrote: > >> The problem with putting _Type on the end of all [sub]type names is that >> it adds no information. > >But that's the whole point! Adding any more information is _undesirable_ >at this point, because presumably an object and its type _both_ Since taking on the learning of Ada95, I have adopted the old Pascal style convention of prefixing 'a' to a capitalized type name: aTree, aList, aStack, etc. In C, I would favor a '_t' suffix, but this appears foreign in Ada source. It just somehow seems impious. Incidentally, the only reason I would use such suffixes is to spare the fundamental type name for use as a variable, e.g. List : aList; Other than that, I'm opposed to elaborate suffix or prefix schemes: that Hungarian Notation thiing is a pet peeve!