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,af3dada69080e420 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-23 03:29:08 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!news.rwth-aachen.de!news-koe1.dfn.de!RRZ.Uni-Koeln.DE!uni-duisburg.de!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.ada Subject: Re: Interesting effects in array renaming Date: Mon, 23 Jun 2003 10:29:08 +0000 (UTC) Organization: GMUGHDU Message-ID: References: <3EF5E6B8.3030203@spam.com> NNTP-Posting-Host: d2-hrz.uni-duisburg.de X-Trace: a1-hrz.uni-duisburg.de 1056364148 21344 134.91.1.15 (23 Jun 2003 10:29:08 GMT) X-Complaints-To: usenet@news.uni-duisburg.de NNTP-Posting-Date: Mon, 23 Jun 2003 10:29:08 +0000 (UTC) User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (HP-UX/B.11.00 (9000/831)) Xref: archiver1.google.com comp.lang.ada:39588 Date: 2003-06-23T10:29:08+00:00 List-Id: Dmitry A. Kazakov wrote: : : "... any constraint implied by the subtype_mark of the : object_renaming_declaration is ingored)." : : I.e. whatever subtype you, a programmer, might specify I, the compiler, will : shamelessly ignore it! : : How safe! Do you really think it is OK? Consider this: [...] : I see only two alternatives: : : Either to add a dynamic semantics ensuring that the result of renaming is a : valid object of the declared subtype. [X2 raises Constraint_Error if : Constrained'Range /= X'Range] I think the compiler could warn about possibly "incompatible" constraints in a renaming declaration. Have you written to the producers of your compiler?