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 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,627a173c3309b242 X-Google-Attributes: gid103376,public Path: controlnews3.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.gamma.ru!Gamma.RU!comstar.ru!teleglobe.net!151.99.250.105.MISMATCH!news.finmeccanica.it!not-for-mail From: "Davide" Newsgroups: comp.lang.ada Subject: Re: Allocation of local constant arrays Date: Thu, 20 May 2004 11:56:35 +0200 Organization: Finmeccanica Message-ID: References: NNTP-Posting-Host: 192.168.54.114 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Xref: controlnews3.google.com comp.lang.ada:702 Date: 2004-05-20T11:56:35+02:00 List-Id: "Robert I. Eachus" ha scritto: > then put everything as constants in the > package body. As a general way to design the software, if you have constants used only by a procedure, do you prefer (for the final application) to nest them in that procedure or to keep them together with all the other constants in the package body, then visible also to procedures not referencing them? The question, in other words, is: locate the data closest as possible to operations who used them or tend to "globalize" their visibility also when not necessary? Waiting for opinions. Davide.