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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC,XPRIO autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9def0a9c238c7bd8,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-02-11 19:30:39 PST Path: supernews.google.com!sn-xit-02!supernews.com!news.tele.dk!128.230.129.106!news.maxwell.syr.edu!newsfeed.skycache.com!Cidera!news-sjo.usenetserver.com!news-out.usenetserver.com!e3500-chi1.usenetserver.com.POSTED!not-for-mail Reply-To: "Peter Richtmyer" From: "Peter Richtmyer" Newsgroups: comp.lang.ada Subject: Ada 0x Wish List X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Message-ID: X-Complaints-To: abuse@usenetserver.com X-Abuse-Info: Please be sure to forward a copy of ALL headers X-Abuse-Info: Otherwise we will be unable to process your complaint properly. NNTP-Posting-Date: Sun, 11 Feb 2001 22:27:45 EST Organization: WebUseNet Corp http://www.usenetserver.com - Home of the fastest NNTP servers on the Net. Date: Sun, 11 Feb 2001 22:25:28 -0500 Xref: supernews.google.com comp.lang.ada:5142 Date: 2001-02-11T22:25:28-05:00 List-Id: Here are a few Ada "improvements" that I would like to see. First couple are minor. Third is ...? 1) In a Package Spec, it would be nice to be able to declare variables that are "constants' to other packages. that is, they can be "read" by other packages, but not written / updated. Code within the package (and child packages, etc) could update these variables like any other variables. e.g.: Package A is B : constant Integer := 5; -- normal constant C : convar integer := 8; -- externally constant, internally variable ... Note the keyword "convar" is used for lack of a better keyword for now. 2) In a subroutine, would like to be able to declare variables that are "persistent", like C "static" variables and only used by the one subroutine. Presently this data must be in the package body (or spec, or some other package spec), where it is visible and updatable by other routines, even though it is intended for use by one routine only. (Or is there another easy way to do this already?) 3) I would like "portable" representation specs. Regardless of the endian-ness of the machine, would like an option (that is required to be implemented for all compilers) so we can write rep specs once and be able to use them on any computer. (Would also like the compilers to continue to support Ada95 rep specs). I could think of a number of different ways to specify these, but I am sure others with compiler-writing experience would have more to say on what is practical. So, please go easy on me, but go at it on the ideas.... :-) For Ada... Peter