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,88e7ef9008757431 X-Google-Attributes: gid103376,public From: "David C. Hoos, Sr." Subject: Re: Function Calls by Address Date: 1999/09/03 Message-ID: <7qp5oo$2un@hobbes.crc.com>#1/1 X-Deja-AN: 520731992 References: <37CADE68.6AF06F5D@escmail.orl.lmco.com> <37CEEFFA.7D73F78D@magic.fr> <7qooh7$hbh$1@nnrp1.deja.com> <37CFFEA6.921CBE59@magic.fr> Organization: Coleman Research Corporation X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Newsgroups: comp.lang.ada Date: 1999-09-03T00:00:00+00:00 List-Id: Francois Godme wrote in message news:37CFFEA6.921CBE59@magic.fr... > Robert Dewar wrote: > > > In article <37CEEFFA.7D73F78D@magic.fr>, > > Francois Godme wrote: > > > I knew about the nested procedures restriction but thought that no one > still uses nested procedures. Personally, I have stopped using them. Why > will I hide a perfectly useful procedure inside another when all I want > is to spare me rewriting over and over the same thing. Are nested > procedures coming from the Pascal heritage where everything was residing > inside the main program? By the same matter, who is still using the > 'separate' construct for writing new applications? Well... sometimes it's handy to have a procedure that would use a number of parameters that are just locally declared variables within the caller. Nesting the procedure saves calling overhead, because being nested it can be parameterless. As far as separates go.. it's frequently wise to use separates for target- dependent code. I also use them to keep down the size of package body files -- e.g., for procedures that have long case constructs, or whatever.