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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC 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: "John G. Volan" Subject: Re: Naming of Tagged Types and Associated Packages Date: 1998/09/06 Message-ID: <35F36963.5C7174E9@sprintmail.com>#1/1 X-Deja-AN: 388591824 Content-Transfer-Encoding: 7bit References: <6qfp80$p0u$1@nnrp1.dejanews.com> <35CD0A8E.21D64380@sprintmail.com> <35CEBAAF.B9B82820@sprintmail.com> <35F0CAF2.9B447FD2@sprintmail.com> <35F2AEEA.94D37DFF@sprintmail.com> X-Posted-Path-Was: not-for-mail Content-Type: text/plain; charset=us-ascii X-ELN-Date: Sun Sep 6 22:04:01 1998 Organization: EarthLink Network, Inc. Mime-Version: 1.0 Reply-To: johnvolan@sprintmail.com Newsgroups: comp.lang.ada Date: 1998-09-06T00:00:00+00:00 List-Id: Brian Rogoff wrote: > > On Sun, 6 Sep 1998, John G. Volan wrote: > > Matthew Heaney wrote: > > > > > > My philosophy is to use the name _Type only as a last resort, as it has > > > a sort of generic quality to it. > > > > Funny, I'd say its precisely this quality that should make _Type the > > *first* resort! :-) It's so generally applicable as a type-marking > > suffix one might as well use it everywhere... > > Exactly my line of thinking too :-|. This is one of the reason's I like > the Dylan convention of delimiting type names with angle brackets; this > convention has the pleasing (to me) effect of making type names look very > different from other lexical items. I assume this makes it possible to do something like: Car : ; Color : ; In other words, the Dylan convention yields what are effectively two completely disjoint namespaces for object names and type names. The marking clearly indicates which namespace a given identifier belongs to. But except for the marking, identifiers in the two namespaces could be identical. Compare that with the style convention in Eiffel, where all-uppercase is used for type names and all-lowercase (or mixed case) is used for entity names. e.g. car : CAR color : COLOR In this case, the language really does maintain two dijoint namespaces. The capitalization scheme is just a convention; Eiffel is actually case-insensitive, but it uses syntactic context to decide which namespace to use at any given point. -- indexing description: "Signatures for John G. Volan" self_plug: "Ex Ada guru", "Java 1.1 Certified", "Eiffelist wannabe" two_cents: "Java would be even cooler with Eiffel's assertions/DBC, % %generics, true MI, feature adaptation, uniform access, % %selective export, expanded types, etc., etc..." class JOHN_VOLAN_SIGNATURE inherit SIGNATURE invariant disclaimer: not (opinion implies employer.opinion) end -- class JOHN_VOLAN_SIGNATURE