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.1 required=5.0 tests=BAYES_05,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e9f44aef4f5aee18 X-Google-Attributes: gid103376,public From: tmoran@bix.com Subject: Re: Access to procedures Date: 1999/06/27 Message-ID: <7l5vpm$mfq@lotho.delphi.com>#1/1 X-Deja-AN: 494517804 References: Organization: Delphi Internet Services Newsgroups: comp.lang.ada Date: 1999-06-27T00:00:00+00:00 List-Id: >> When working on my GUI classes, I have been a VERY happy camper to have >> Unrestricted_Access around for quick testing and even for small little apps >> that use the classes. > >If it makes you a happy camper, how can it be bad? If it feels good at the time, it must be good? How about "Use Unrestricted_Access when appropriate, but don't make a habit of it". There are almost always better ways to solve the problem. Practice learning and using them.