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,3d3f20d31be1c33a X-Google-Attributes: gid103376,public X-Google-Thread: f43e6,2c6139ce13be9980 X-Google-Attributes: gidf43e6,public X-Google-Thread: 1108a1,2c6139ce13be9980 X-Google-Attributes: gid1108a1,public X-Google-Thread: fac41,2c6139ce13be9980 X-Google-Attributes: gidfac41,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Interface/Implementation (was Re: Design by Contract) Date: 1997/09/11 Message-ID: #1/1 X-Deja-AN: 271684846 References: Organization: New York University Newsgroups: comp.object,comp.software-eng,comp.lang.ada,comp.lang.eiffel Date: 1997-09-11T00:00:00+00:00 List-Id: <> This makes no sense, you arrange the subprograms in a package body in any order that you please, I don't know whose code you have been reading, but this does not make sense. First, why are you "reading" package bodies at all in this sense, I can't see this as a useful activity. What you might want to do is to read through the specificatoins that are part of a body, but these of course can be in any order you please. Then you read the subprogram implementations if you want, and of course these can be in any order you please. So to be clear, the typical structure of an Ada package body (we are talking now about the ordering of sections of code) is as follows: Collection of subprogram specifications in any order you please followed by Collection of subprogram bodies in any order you please, which need not be the same order as used for the subprogram specifications. Where exactly is the dreaded ordering dependency here that is causing you so much grief?