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.3 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI,
	REPLYTO_WITHOUT_TO_CC autolearn=no 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-13 21:44:05 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!arclight.uoregon.edu!fr.usenet-edu.net!usenet-edu.net!enst!enst.fr!not-for-mail
From: Christoph Grein <christoph.grein@eurocopter.com>
Newsgroups: comp.lang.ada
Subject: Re: code partitioning (was: Future with Ada)
Date: Thu, 14 Mar 2002 06:41:54 +0100 (MET)
Organization: ENST, France
Sender: comp.lang.ada-admin@ada.eu.org
Message-ID: <mailman.1016084642.17231.comp.lang.ada@ada.eu.org>
Reply-To: comp.lang.ada@ada.eu.org
NNTP-Posting-Host: marvin.enst.fr
Mime-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
X-Trace: avanie.enst.fr 1016084643 7104 137.194.161.2 (14 Mar 2002 05:44:03
 GMT)
X-Complaints-To: usenet@enst.fr
NNTP-Posting-Date: Thu, 14 Mar 2002 05:44:03 +0000 (UTC)
Return-Path: <christoph.grein@eurocopter.com>
Content-MD5: DGRNORcG3/oIxfdMFzAv1w==
X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc 
Errors-To: comp.lang.ada-admin@ada.eu.org
X-BeenThere: comp.lang.ada@ada.eu.org
X-Mailman-Version: 2.0.8
Precedence: bulk
X-Reply-To: Christoph Grein <christoph.grein@eurocopter.com>
List-Help: <mailto:comp.lang.ada-request@ada.eu.org?subject=help>
List-Post: <mailto:comp.lang.ada@ada.eu.org>
List-Subscribe: <http://ada.eu.org/mailman/listinfo/comp.lang.ada>,
	<mailto:comp.lang.ada-request@ada.eu.org?subject=subscribe>
List-Id: comp.lang.ada mail<->news gateway <comp.lang.ada.ada.eu.org>
List-Unsubscribe: <http://ada.eu.org/mailman/listinfo/comp.lang.ada>,
	<mailto:comp.lang.ada-request@ada.eu.org?subject=unsubscribe>
Errors-To: comp.lang.ada-admin@ada.eu.org
X-BeenThere: comp.lang.ada@ada.eu.org
Xref: archiver1.google.com comp.lang.ada:21190
Date: 2002-03-14T06:41:54+01:00

> I prefer
> 
>     meaningful_name := some * weird * and / long + expression;
>     case meaningful_name is
>     end case; -- meaningful_name
> 
> Introducing local variables can improve readability.

This is not the point. Of course this is sensible. My proper point against this proposal is:

Since a case statement has an expression syntactically, the expression would 
have to be repeated at the end

case expression is
  ..
end case expression;

and this is against the spirit of repeating only a short identifier (the 
defining_designator etc.) at the end.

Thus the proper way would be a {case_}statement_identifier:

[{case_}statement_identifier:]
case expression is
  ...
end case [{case_}identifier];

[The curly braces stand here for what is printed in italics in the RM.]

This is the only form I would like to see as a future syntax enhancement. We 
already have this for loops and blocks, so why not for ifs and cases (and 
selects).

We do not need weird new syntax rules.