From owner-sc22wg5@dkuug.dk Tue Jul 8 21:11:13 2003 Received: (from majordom@localhost) by dkuug.dk (8.12.8p1/8.9.2) id h68JBDdZ046922 for sc22wg5-domo; Tue, 8 Jul 2003 21:11:13 +0200 (CEST) (envelope-from owner-sc22wg5@dkuug.dk) X-Authentication-Warning: ptah.dkuug.dk: majordom set sender to owner-sc22wg5@dkuug.dk using -f Received: from out4.mx.nwbl.wi.voyager.net (out4.mx.nwbl.wi.voyager.net [169.207.3.122]) by dkuug.dk (8.12.8p1/8.9.2) with ESMTP id h68JAmEc046917 for ; Tue, 8 Jul 2003 21:11:08 +0200 (CEST) (envelope-from Craig_Dedo@execpc.com) Received: from execpc.com (d35.as16.nwbl1.wi.voyager.net [169.207.89.35]) by out4.mx.nwbl.wi.voyager.net (Postfix) with ESMTP id 1EB2BC37E2 for ; Tue, 8 Jul 2003 14:10:41 -0500 (CDT) Message-ID: <3F0B174D.1050906@execpc.com> Date: Tue, 08 Jul 2003 14:11:09 -0500 From: Craig Dedo Reply-To: Craig Dedo Organization: Elmbrook Computer Services User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: WG5 Mailing List Subject: Nesting of Submodules (Was: (SC22WG5.2854) Straw votes to ponder concerning Modules TR) References: <200307021755.h62HtGgM006819@dkuug.dk> <200307081808.h68I8hxG046526@dkuug.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-sc22wg5@dkuug.dk Precedence: bulk Bill Long wrote: > > I believe an additional question is reasonable for a straw vote: > > Should a submodule be allowed as a parent of another submodule? > > ------------------------------------------------------------------------------- > > > I vote NO on this. I think that allowing multiple layers of > submodules is a gratuitous complication that serves no real purpose. > Further, there is the usual problem of specifying that something is > allowed to be nested to unspecified levels: actual implementations > are allowed to put a limit on the number of levels under the size and > complexity exemption. This can limit portability. I'd prefer to avoid > this issue from the start and say that the parent of a submodule must > be a module. > > > Cheers, > Bill I disagree. There is a well known and proven solution to the problem of nesting to unspecified levels. All we need to do is specify a minimum number of levels, with the option of exceeding this minimum. We do that in a number of other cases, e.g.: * Number of array dimensions * Number of characters per physical source line * Number of physical source lines per logical source statement In comparison, the C and C++ standards go far beyond what Fortran does and actually have long lists of minimum translation and implementation limits. The text is quite easy to write. We could say something like, "The processor shall allow nesting of at least 100 submodules." Or, use whatever other number you believe is reasonable. Other than the nesting limit issue, are there any other complications with nesting submodules? -- Sincerely, Craig T. Dedo 17130 W. Burleigh Place E-mail: Craig_Dedo@execpc.com Brookfield, WI 53005-2759 Voice Phone: (262) 783-5869 USA Fax Phone: (262) 783-5928 "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin (1759)