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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,25d835bb9a4a003f X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,CP1252 Path: g2news2.google.com!postnews.google.com!p35g2000yqh.googlegroups.com!not-for-mail From: =?ISO-8859-1?Q?Hibou57_=28Yannick_Duch=EAne=29?= Newsgroups: comp.lang.ada Subject: Re: Types, packages & objects : the good old naming conventions question (without religious ware) Date: Sat, 31 Oct 2009 05:38:32 -0700 (PDT) Organization: http://groups.google.com Message-ID: <1a201412-454a-4994-af72-9e1e9840e248@p35g2000yqh.googlegroups.com> References: <4ae9dade$0$6551$9b4e6d93@newsspool4.arcor-online.net> <30ad5ea8-955e-45c0-ae94-c84927cdb2b8@d5g2000yqm.googlegroups.com> <1pldds3sao0zf$.1h9y0q8qmnks1$.dlg@40tude.net> NNTP-Posting-Host: 77.198.58.237 Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1256992712 21754 127.0.0.1 (31 Oct 2009 12:38:32 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Sat, 31 Oct 2009 12:38:32 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: p35g2000yqh.googlegroups.com; posting-host=77.198.58.237; posting-account=vrfdLAoAAAAauX_3XwyXEwXCWN3A1l8D User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; fr),gzip(gfe),gzip(gfe) Xref: g2news2.google.com comp.lang.ada:8923 Date: 2009-10-31T05:38:32-07:00 List-Id: On 31 oct, 12:47, "Dmitry A. Kazakov" wrote: > On Sat, 31 Oct 2009 04:30:38 -0700 (PDT), Hibou57 (Yannick Duch=EAne) wro= te: > > On 31 oct, 10:49, "Dmitry A. Kazakov" > > wrote: > >> "the cats" > > This is a class, not a type > > So let's call classes The_Xxxs (with an ending S) > > But what about types ? (and instances of a type) > > Class is a set of types. Type is a set of values. When the cat is an > object, the cats is its type. Mammals is the set of types that contain th= e > type cats. The corresponding type can be the mammals, i.e. flatten mammal= s > class. You are right, this is not a class. But the type may rather be seen as an abstraction of each individual instance (or as a representation of all the possible instances, thus the set, but not as a set of instances). The type, provide the way to create an instance, it may be used to create a set of value, but it is not a set of value (I know you use type right, I'm just trying to make terms clear). So let say now your =AB The Cats =BB is a type, and finally there is something which mark it, so this goes in the way of a mark to state a name is used a a type. =93 The =94 and the plural, may be seen as equivalent to the =93 _Type =94 The only disclaimer I would add, is that I would not name a type using a plural. This may seems natural at the type definition, but this will be less natural at object instantiations (unless the type is a containers, and the containers is named after the concrete type of items it contains). > In Ada there is no notation for the class. T'Class is a type, the closure > of the class rooted in T, i.e. all values of the members of types derived > from T. This do the job, isn't it ? And this is true that a type =97 which may be, at least potentially =97 the subject of any number of derivations, at least potentially stands for a class, even it is not actually derived. So there is no trouble to get the class rooted at a type from a type attribute. There is no need for an explicit declaration of a class, because the class associated to a tagged type, always exist, that's the concept, and does not need any declaration (the subtype is there, if a declaration is needed or wished). Thanks for having notice (I mean, thanks for the correction)