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,e94a7e4f6f888766 X-Google-Attributes: gid103376,public From: Richard D Riehle Subject: Re: Self-referential types Date: 1999/10/22 Message-ID: <7uq8g3$jl8$1@nntp5.atl.mindspring.net>#1/1 X-Deja-AN: 539341763 References: <7ttb4a$8mq$1@nnrp1.deja.com> <3802f2db_2@news1.prserv.net> <3803B5E3.F96A6DD4@mitre.org> <3803c8bc_2@news1.prserv.net> <3804E7E0.6A0265FB@mitre.org> <38077EB3.E6911567@mitre.org> <7u86su$o5v$1@nntp8.atl.mindspring.net> <380BA036.E9F51F22@mitre.org> Organization: MindSpring Enterprises X-Server-Date: 22 Oct 1999 17:56:19 GMT Newsgroups: comp.lang.ada Date: 1999-10-22T17:56:19+00:00 List-Id: In article <380BA036.E9F51F22@mitre.org>, "Robert I. Eachus" wrote: > To specifically address Richard Riehle's comments, I tend to do the >same thing as he does with case statements, but I unnest the case >alternatives and put them in a package. If there is local state needed >from the enclosing procedure, I make it a generic package and >instantiate it locally to pass the parameters of the enclosing >procedure. I agree with this principal. In fact, with the advent of private child packages, one can promote these little procedures to a next level above the procedure in which they would have been nested and leverage their visibility through private package specifications within the same parent-child hierarchy. As you so carefully note in your message, this does require some planning. In a large-scale development effort, planning at this level of detail is often absent from the process. Richard Riehle http://www.adaworks.com