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,dbf84a1c2794f4fb X-Google-Attributes: gid103376,public From: "Norman H. Cohen" Subject: Re: packages and private parts Date: 1997/02/14 Message-ID: <3304E6C8.11E6@watson.ibm.com>#1/1 X-Deja-AN: 218878224 References: <32F170C8.6A88F208@cam.org> <32FA4C67.48D9@watson.ibm.com> <32FB51D8.1C90@watson.ibm.com> Content-Type: text/plain; charset=us-ascii Organization: IBM Thomas J. Watson Research Center Mime-Version: 1.0 Reply-To: ncohen@watson.ibm.com Newsgroups: comp.lang.ada X-Mailer: Mozilla 3.0 (Win95; I) Date: 1997-02-14T00:00:00+00:00 List-Id: Speaking of concerns that child visibility into private parts of parent packages could be harmful, Robert Dewar wrote: > My memory was that VERY few people were convinced, I certainly > was not, I thought the suggestion of absolute privacy was a serious mistake, > and i still do, and that is the same view that a majority of people had! For the record, my memory is quite different. I recall that, at least early in the Mapping Phase of the Ada 9X project, many of the reviewers--including Robert--were seriously concerned about this issue. Tucker had to fight hard to defend the rule, but did so skillfully and eventually won most of us over, including me. It is not unheard of for Robert to forcefully argue different sides of an issue on different occasions, but I suspect that Robert is remembering of a later stage of the Ada 9X project than I am. > Certainly it would be perectly fine to add a pragma restricting visibility > in the manner Norman suggests, but this issue has never come up among the > thousands of people actually using Ada 95, so it seems to me this is a > case where the majority and Tuck and the RM all agree, and it's a good > thing that they do! Let me clarify that "in the manner Norman suggests" is meant to modify "restricting visibility", not "pragma". I do not agree that it would be "perfectly fine" for an implementation to add a restriction making a unit that is legal according to the standard illegal for a particular implementation, except in the absence of an implementation-defined pragma. On the other hand, there is nothing wrong with an implemenation-defined pragma pragma Subject_To_Change ( entity-name ); to flag entities declared in the private part of a package, so that a compiler would generate a WARNING if the named entity were later referrerd to in the private part of a child. When Robert says that "this issue has never come up among the thousands of people actually using Ada 95", he really means that ACT has not received a request for such a pragma. Not much can be inferred from that fact, except perhaps that the usefulness of such a pragma has not been widely discussed until now. -- Norman H. Cohen mailto:ncohen@watson.ibm.com http://www.research.ibm.com/people/n/ncohen