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=-0.1 required=5.0 tests=BAYES_00,FREEMAIL_FROM, FROM_STARTS_WITH_NUMS,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c319c681003d3e4c X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1994-09-21 06:59:17 PST Path: bga.com!news.sprintlink.net!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!zombie.ncsc.mil!paladin.american.edu!auvm!COMPUSERVE.COM!73672.2025 Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU Newsgroups: comp.lang.ada Message-ID: <940919234028_73672.2025_DHR68-1@CompuServe.COM> Date: Mon, 19 Sep 1994 19:40:29 EDT Sender: Ada programming language From: Ken Garlington <73672.2025@COMPUSERVE.COM> Subject: Re: Static in 9X Comments: To: "comp.lang.ada" Date: 1994-09-19T19:40:29-04:00 List-Id: It appears that both Robert Dewar and Tucker Taft believe that the issue of whether or not objects can be placed in ROM is generally unrelated to the issue of whether or not the expression is static. Since we also originally asked our vendor not to use "static" as a basis for their proposal, we must understand Ada better than I thought! :) Now, if we can only get our _vendor_ to accept this profundity at our next meeting... While I'm at it, I also wanted to thank Mr. Taft for explaining the difficulty of optimizing an expression initialized with a previosuly-defined constant composite/attribute. Although the problem of keeping the composite in memory long enough wouldn't necessarily be a problem for a VAX/1750A cross-compiler (generally, the most data that could be in one package on a 1750A is 32K, which a VAX can certainly support), I can see that the practice of using common compiler components for multiple host/target combinations would make it difficult to do this in practice.