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-25 07:23:36 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsfeed.stueberl.de!eusc.inter.net!cs.tu-berlin.de!uni-duisburg.de!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.ada Subject: Re: Interesting effects in array renaming Date: Wed, 25 Jun 2003 14:23:35 +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 1056551015 5089 134.91.1.15 (25 Jun 2003 14:23:35 GMT) X-Complaints-To: usenet@news.uni-duisburg.de NNTP-Posting-Date: Wed, 25 Jun 2003 14:23:35 +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:39729 Date: 2003-06-25T14:23:35+00:00 List-Id: Dmitry A. Kazakov wrote: : : But the "usual" meaning of "renames" is: : : p : renames a; Opening the question of why theree is a subtype mentioned in a renaming declaration. (Which I cannot answer, but I find it consistent with other declarations, which involves a subtypes name most of the times. Would you like p: constant := a; ?) :> Should renaming be for imposing constraints? :> If I rename myself as Bouwhouws, that won't change me I think, :> and it doesn't impose a constraint on me. : : It imposes a constraint on people calling you. I'd rather say it offers them the freedom to call me by that other name, which additional freedom is not a constraint. : Consider : renaming Mr.Smith to Mrs.Smith. I think this is an example of changing the type (in some humans typing scheme), or, if not, of changing the view, but _not_ the name, which is "Smith". "Smith, come here, carry that chair!" : I give you another example. When you rename a routine: : : procedure Baz (A : Apple); : procedure Foo (B : Apple) renames Baz; : : the compiler checks the specified parameter profile. According to your : theory it should not. Indeed : : procedure Foo (B : Orange) renames Baz; : : by no means changes Baz. Well, if constraints and parameter profiles should get the same treatment for reasons of consistency wrt to the criterion "checked" in renaming declarations, then, have you checked the implications of such a change? I can't do this but after reading Robert's comments, I trust this has been considered, with the result known. I still think that a compiler warning will be useful. -- georg