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
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,b47b15fda2aeb0b2
X-Google-Attributes: gid103376,public
From: dewar@cs.nyu.edu (Robert Dewar)
Subject: Re: Two ideas for the next Ada Standard
Date: 1996/09/01
Message-ID: <dewar.841590773@schonberg>#1/1
X-Deja-AN: 177826346
references: <50aao3$3r88@news-s01.ny.us.ibm.net>
organization: Courant Institute of Mathematical Sciences
newsgroups: comp.lang.ada
Date: 1996-09-01T00:00:00+00:00
List-Id: <comp.lang.ada>


Responding to Leonid Dulman's suggestions

     1. ALIASED is more common notion then RENAMES  and  (it seams to me)
        this key word needn't.

         Incomprehesible, not close enough to English to guess the intent!

     2. OUT parameters have such chances as IN OUT

         Incomprehesible, not close enough to English to guess the intent!

     3. Maybe  for calling entry in SELECT statement with  DELAY to write
        in the form :

        <entry_name>(...)   WITH DELAY [UNTIL] <time>;

        ACCEPT <entry_name>(...) WITH DELAY [UNTIL] <time> DO ...   END;

        This construction will  allow to expect rendezvous  up to a given
        time moment, or given time interval.

          This is redundant and unnecessary syntax, this functionality is
          already available in convenient form.

     4. To add the subroutine parameter type ALIASED, that will  allow to
        use inside it reference to the subroutines with  " 'ACCESS " or
        " 'UNCHECKED_ACCESS" parameters.

          Seems bogus, since if a parameter is passed by copy, what would
          it mean to take its acccess. Do you intend this to force call
          by reference

     5. Nongeneric form of packages  DIRECT_IO and SEQUENTIAL_IO.
        Parameter RECORD_SIZE to add for  parameter's  list in procedures
        CREATE and OPEN
        (for example in form RECORD_SIZE:=<type's name>'size;).

          Very confused, how could you pass data items to this without
          having a generic formal type parmeter. I suspect what you
          want can perfectly easily be provided using Stream_IO, but
          the suggestion is too confused to be sure.

     6. To specify use ACCESS and UNCHECKED_ACCESS attributes for aliased
        variable. Now (in basic) it is necessary to use  UNCHECKED_ACCESS
        attribute.

          Incomprehensible, another possible language problem?