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: John Volan Subject: Re: Naming of Tagged Types and Associated Packages Date: 1998/08/10 Message-ID: <35CFB300.242CC40D@ac3i.dseg.ti.com>#1/1 X-Deja-AN: 379921911 Content-Transfer-Encoding: 7bit References: <6qfp80$p0u$1@nnrp1.dejanews.com> <6qnbms$ld7$1@nnrp1.dejanews.com> Content-Type: text/plain; charset=us-ascii Organization: Raytheon Systems Company, Advanced C3I Systems Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1998-08-10T00:00:00+00:00 List-Id: Brian Rogoff wrote: > > Well, its definitely lexically distinguishable in a case sensitive > language, but as I said earlier, I find it aesthetically unappealling to ^^^^^^^^^^^^^^^^^^^^^^^^^^ > rely on case alone for the distinction. Even in C and Java, I use > more than case to distinguish. Personally, I don't mind a little > redundancy, and I find all of this talk of "noise" in the type name really > funny, as though its somehow really difficult for the reader to deal with > this _Type business. Although I don't count myself among them [*], I'm pretty sure that the people who object to the "_Type" convention in Ada do so not because they feel that this "noise" somehow reduces understandability, but rather purely as a matter of taste. To them, having a type name _say_ that it is a type name, when this fact can simply be deduced from context, or by looking up the declaration, amounts to "catering to the programming language". This seems to disturb their aesthetic sensibilities somehow -- just as relying on case distinctions seems to disturb your aesthetic sensibilities, Brian. [*] I should say, I don't object to "_Type" -- and indeed I advocate it -- if one is programming in Ada. It seems to be the best compromise given the properties of that language. On the other hand, if one is programming in Java, C++, Eiffel, or Smalltalk, I'd advocate exploiting case conventions for all they're worth, and don't bother with "_Type". > However, as I also said, if I were to use Eiffel or a similar language > long enough, I'm pretty sure I'd get used to it, even if I don't like > that convention now. Exactly. -- Signature volanSignature = new Signature ( /*name: */ "John G. Volan", /*employer: */ "Raytheon Advanced C3I Systems, San Jose", /*workEmail: */ "johnv@ac3i.dseg.ti.com", /*homeEmail: */ "johnvolan@sprintmail.com", /*selfPlug: */ "Sun Certified Java Programmer", /*twoCents: */ "Java would be even cooler with Ada95's " + "generics, enumerated types, function types, " + "named parameter passing, etc...", /*disclaimer:*/ "These views not packaged in COM.ti.dseg.ac3i, " + "so loading them throws DontQuoteMeError. :-)" );