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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,71c743c03ed191fe X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-09-23 11:16:18 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!news.stealth.net!news.stealth.net!nntp5.savvis.net!uunet!dfw.uu.net!ash.uu.net!spool0901.news.uu.net!spool0900.news.uu.net!reader0901.news.uu.net!not-for-mail Date: Mon, 23 Sep 2002 14:18:20 -0400 From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Beginer problem: variable array size References: <1032789075.864322@master.nyc.kbcfp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Organization: KBC Financial Products Message-ID: <1032804973.357894@master.nyc.kbcfp.com> Cache-Post-Path: master.nyc.kbcfp.com!unknown@mosquito.nyc.kbcfp.com X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/) NNTP-Posting-Host: 204.253.250.10 X-Trace: 1032804975 reader1.ash.ops.us.uu.net 3904 204.253.250.10 Xref: archiver1.google.com comp.lang.ada:29290 Date: 2002-09-23T14:18:20-04:00 List-Id: tmoran@acm.org wrote: > If you can't show such a program, then I'd like to know what in > fact are its limits, either as a constant like 8*3600 or 10_000_000 > or by a formula like "System_RAM_In_Bytes/2" or some such thing. How very odd. You yourself posted a program which meets the OP's requirements. In the terms you describe above, can you tell me what the limits are of your program? There is a fundamental difference between a program which has a wired-in size limit and a program which is bound by available memory, or even available address space. For one thing, when the latter program is moved to a system with more resources, it will hndle larger inputs. The former program will be stuck at its limit until it's revised. My former office mate held by the rule of "zero, one, or infinity" when it came to allowable limits. I have seen this rule violated to much distress. The latest example occurred just weeks ago, when the risk management system we use was discovered to have a hard limit of one hundred different security types.