From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=3.0 tests=BAYES_20 autolearn=ham
	autolearn_force=no version=3.4.5-pre1
Date: 3 Dec 92 16:57:38 GMT
From: dog.ee.lbl.gov!overload.lbl.gov!agate!linus!linus.mitre.org!news!emery@uc
bvax.Berkeley.EDU  (David Emery)
Subject: Re: (none)
Message-ID: <EMERY.92Dec3115738@dr_no.mitre.org>
List-Id: <comp.lang.ada>

There are a few things in Ada that don't help writing modular code.
Large case statements are one.  Another is the requirement that all
task entry accept statements have to be in the main body of the task
(i.e.  they can't be in a subroutine within the task.)  

Once I coded a 500-600 line task body, most of which was a 300 line
accept statement.  This was full of nested accepts, etc.  (This was
the key part of a distributed simulation framework, where part of the
distribution was achieved through Ada tasks.  The task entry logic was
quite complex to identify and resolve deadlock situations that were
part of the Misra-Chandy distributed simulation variant that we were
implementing.)

I don't know if Ada9X helps "fix" this problem. 

But, I agree that the right solution is to "fix" the coding standard.

				dave