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.1 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,75ffc1f081ec10e3 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!news3.google.com!news4.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.megapath.net!news.megapath.net.POSTED!not-for-mail NNTP-Posting-Date: Thu, 06 Jul 2006 17:28:38 -0500 From: "Randy Brukardt" Newsgroups: comp.lang.ada References: <12ad8guf3sg1o0d@corp.supernews.com> <1loq7utmaxvll$.yqsxj5edzqgv.dlg@40tude.net> <12afs64kh432q0e@corp.supernews.com> <12aihj2lrjqpc3a@corp.supernews.com> <7bednaJHX_FTMDTZnZ2dnUVZ_uudnZ2d@megapath.net> <12ak5urrrj6d756@corp.supernews.com> Subject: Re: Constant record components Date: Thu, 6 Jul 2006 17:29:24 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Message-ID: NNTP-Posting-Host: 64.32.209.38 X-Trace: sv3-ZWnwt7PNu6Ak173ypilz8ua1g6Sh/gK43jxK19UvVipythW3rR62QDrnCPzorlH1/VSwMHFnWbRgmQy!K9Skt2/CKm/tbAor9rdwt0rDDx9/0mJoFEdFkGT/DFy//syqSCzQtBDXQj+ts+heHViFoEIRS4Qi!Wd1N75rFz1pAtQ== X-Complaints-To: abuse@megapath.net X-DMCA-Complaints-To: abuse@megapath.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 Xref: g2news2.google.com comp.lang.ada:5543 Date: 2006-07-06T17:29:24-05:00 List-Id: "Jean-Pierre Rosen" wrote in message news:p6fi8e.de4.ln@hunter.axlog.fr... > Randy Brukardt a �crit : > > > > I can say that the notion that something declared "constant" could in fact > > be assigned to in some scope is rather disgusting. I don't think it would > > fly. > > > Hmmm.... Initialization of controlled constants? After initialization, of course. (Constants are assign-once, logically. Assign-never would be a problem, because they'd have no value at all in that case!) And similarly, before finalization (although it shouldn't really be necessary to clear the finalized result -- but it is often done, and harmless to do). Still, allowing the assignment of a name that is declared to be a constant view at some point between initialization and finalization would be a nasty change to the language. (Note that it might be possible to assign via a different name; that's a different issue -- and one that is usually a programming error.) Otherwise, "constant" would essentially be meaningless -- bringing us back to the beginning; if it doesn't mean anything, why bother with it at all? Randy.