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/12 Message-ID: <5l673t$k0d@bcrkh13.bnr.ca>#1/1 X-Deja-AN: 240988930 References: <5kjvcv$evt@news.cis.nctu.edu.tw> <3373EAB5.73A0@sprintmail.com> <33755EF7.1A8F@erols.com> Organization: Prism Systems Inc. Newsgroups: comp.lang.ada Date: 1997-05-12T00:00:00+00:00 List-Id: In article , Robert Dewar wrote: >John G. Volan wrote: > >> But once again, I'd want the rule to be simple and minimalistic: Just >> always mark access types (and access objects) with "_Pointer". > >Bad suggestion. Access types are NOT pointers. They may be implemented using >pointers some of the time (but not all the time -- we often find people You are assuming that a pointer is a lower level construct, that is, a machine address. Whether this is true depends on the context. If an assembly language programmer speaks about pointers, he or she probably means address words. A Pascal programmer might use the word to designate the high level reference type of that language. An access type is basically a pointer. You can say that a URL embedded in someone's web page is also a pointer of sorts.