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,92c39a3be0a7f17d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-03-16 07:47:00 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!news.net.uni-c.dk!not-for-mail From: Jacob Sparre Andersen Newsgroups: comp.lang.ada Subject: Re: code partitioning (was: Future with Ada) Date: Sat, 16 Mar 2002 16:46:22 +0100 Organization: Centre for Chaos and Turbulence Studies, Niels Bohr Institute Message-ID: <3C9368CE.A1516DE6@nbi.dk> References: NNTP-Posting-Host: alf.nbi.dk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.net.uni-c.dk 1016293616 27560 130.225.212.55 (16 Mar 2002 15:46:56 GMT) X-Complaints-To: usenet@news.net.uni-c.dk NNTP-Posting-Date: Sat, 16 Mar 2002 15:46:56 +0000 (UTC) X-Mailer: Mozilla 4.78 [en] (X11; U; OSF1 V4.0 alpha) X-Accept-Language: fo,da,no,sv,is,de,fr,en Xref: archiver1.google.com comp.lang.ada:21334 Date: 2002-03-16T16:46:22+01:00 List-Id: Christoph Grein wrote: > Thus the proper way would be a {case_}statement_identifier: > > [{case_}statement_identifier:] > case expression is > ... > end case [{case_}identifier]; Agreed. And this would actually be a nice way to clarify code a bit. On the other hand, should if statements also have this possibility? I would like to be allowed to include the name of the defined record type after "end record". I am aware that record definitions, unlike case statements can not be nested, so this is not nearly as important. > We do not need weird new syntax rules. Generally not. Jacob -- "The current state of knowledge can be summarised thus: In the beginning, there was nothing, which exploded."