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,FREEMAIL_FROM, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,86ec22e070e319c0 X-Google-Attributes: gid103376,public From: warwicks@telusplanet.net (Chris Warwick) Subject: Re: How do I get this to work?? Date: 1999/01/16 Message-ID: #1/1 X-Deja-AN: 433237374 References: <76s0dp$1v4$1@nntp3.uunet.ca> <76tbvv$ba5$1@nntp3.uunet.ca> <770ifd$qui$1@goblin.uunet.ca> <771bl9$sla$1@nnrp1.dejanews.com> <77b9cp$5kh$1@nnrp1.dejanews.com> X-Trace: news2.telusplanet.net 916465574 161.184.43.175 (Fri, 15 Jan 1999 22:46:14 MDT) Organization: gerf inc. NNTP-Posting-Date: Fri, 15 Jan 1999 22:46:14 MDT Newsgroups: comp.lang.ada Date: 1999-01-16T00:00:00+00:00 List-Id: In article <77b9cp$5kh$1@nnrp1.dejanews.com>, robert_dewar@my-dejanews.com wrote: >I notice that a lot of people, especially former C >programmers greatly overuse aliased variables. There >was a reason for completely excluding such variables >from the Ada 83 language, and good practice in Ada 95 >is to absolutely minimize their use. >Remember that aliased variables were introduced for >limited purposes in Ada 95, if you find yourself making >everything aliased, you are probably not organizing >things in an appropriate manner. This thread has wandered off into the theory behind Ada, for that I apologize, and thank everyone for their patience... I will admit some guilt at being a "reformed" C programmer... But, what I find odd is the concept that pointing to an object on the "stack" is poor practice. Even from my Ada83 days, the only "safe" way to do dynamic memory allocation was though the use of local variables on the stack. If I understand this concept, then the view is that it is better to point to a newly allocated buffer, then it is to point to a procedure's local variable. Given that most Ada compilers have no way to deallocate memory, I seem to be trading the potential for a pointer to exist past the life of the allocated memory for a program continously allocates memory...