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=0.8 required=5.0 tests=BAYES_00,INVALID_DATE, MSGID_SHORT,REPLYTO_WITHOUT_TO_CC,T_FILL_THIS_FORM_SHORT autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!watmath!clyde!att!pacbell!ames!ncar!gatech!hubcap!billwolf From: billwolf@hubcap.clemson.edu (William Thomas Wolfe,2847,) Newsgroups: comp.lang.ada Subject: Re: Submitting Ada 9X revision requests Message-ID: <4063@hubcap.UUCP> Date: 11 Jan 89 14:48:41 GMT References: <5816@medusa.cs.purdue.edu> Sender: news@hubcap.UUCP Reply-To: wtwolfe@hubcap.clemson.edu List-Id: >From article <5816@medusa.cs.purdue.edu>, by rjh@cs.purdue.EDU (Bob Hathaway): > Is there any way to get > feedback or proposal information for the Ada 9X extension? I think there > have been several worthwhile ideas presented so far. Below is an excerpt from AJPO's 9X announcement at Tri-Ada '88: ----------------------------- cut here ----------------------------------- "Requests should be focused on language changes that have significant utility to a wide group of Ada users. All requests must be accompanied by sound, well-articulated justifications. Ada commentaries previously approved by the AJPO will automatically be considered during this revision process and need not be resubmitted. [...] Requests should be sent either via electronic mail to Ada9X@ajpo.sei.cmu.edu or via surface mail to: Ada Joint Program Office Ada 9X Project Room 3E114, Pentagon Washington, D.C. 20301-3080 All requests will be made available to the public via electronic means through the Ada Joint Program Office." ----------------------------- cut here ----------------------------------- Ada 9X Revision Request ======================= DATE: (Provide date that the request is prepared) NAME: (Provide name of the individual who has prepared the request) ADDRESS: (Provide the name of the individual's organization and mailing address, including an e-mail address if applicable) TELEPHONE: (If request is from outside the US, please include the appropriate country and city codes) ANSI/MIL-STD-1815A REFERENCE: (If no chapter is particularly relevant, please so state) PROBLEM: (Briefly state the problem. Indicate the most critical aspects to be kept in mind for arriving at a solution, particularly if only a partial solution is possible) IMPORTANCE (Scale of 1 - 10, with 10 being the most important): (Provide a rating for the importance of the request with respect to the overall Ada community, and discuss the consequences if the request is not satisfied by the revision) WORKAROUNDS: (Provide specific examples of workarounds currently being used that allow a partial solution to the problem) POSSIBLE SOLUTIONS (Optional): (Discuss possible solutions for addressing the stated problem)