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,INVALID_MSGID,
	LOTS_OF_MONEY autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,2907a68906511623
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Idea for Ada 200x: Arguments that are procedures
Date: 1998/07/03
Message-ID: <dewar.899492862@merv>#1/1
X-Deja-AN: 368483378
References: <6nh9f0$66i@netline.jpl.nasa.gov> <swhalenEvI788.43x@netcom.com>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 899493184 29763 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-07-03T00:00:00+00:00
List-Id: <comp.lang.ada>


Steve says

<<I couldn't find the old discussions of this particular issue in the
Mapping / Revision Team stuff, or the Language Study Notes.  However,
if there was no better reason for keeping this feature out of the
language than that implementations using displays would have problems,
I think this "fix" absolutely should make it into Ada200x.
>>

There clearly will not be an anaologous development effort for Ada 200x
(compared to Ada 9X). FOr one thing the multi-million dollar funding
ncessary for such an approach is not there, and second, I don't think
anyone thinks it is appropriate at this stage.

Instead we can expect to see implementations introduce extensions that
are genuinely useful for Ada users on a gradual basis, and if and when it
is time for a new standard, it is more likely to be a ratification and
refinement of such existing extensions.

For example, the Size attribute, *particularly* in Ada 95, where the
situation has got worse due to some (in my opinion) injudicious choices
to be incompatible with most existing Ada 83 implementations, obviously
needs work. The Object_Size and Value_Size attributes in GNAT are 
essentially a proprosal in the direction of fixing this. Perhaps this
is not the best solution, but experimentation of this type is clearly
the right way to go in terms of implementing new features.

Of course this will tend to be driven by large serious users of Ada, but
that is as it should be. There are as in any language design a large
diverse collection of ideas from language enthusiasts (for example, there
are some who would go FAR beyond the limited access proposal, and insist
on full closures), but real users doing real applications are always a
somewhat more credible source of input on what the real problems are!