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=2.0 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC,UNRESOLVED_TEMPLATE autolearn=no
	autolearn_force=no version=3.4.4
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!nike!ucbcad!ucbvax!QZCOM.MAILNET!Mats_Ohlin_FOA2
From: Mats_Ohlin_FOA2@QZCOM.MAILNET
Newsgroups: net.lang.ada
Subject: Re: parameter passing
Message-ID: <209283@QZCOM>
Date: Thu, 30-Oct-86 18:08:27 EST
Article-I.D.: QZCOM.209283
Posted: Thu Oct 30 18:08:27 1986
Date-Received: Fri, 31-Oct-86 03:16:49 EST
References: <12245715934.25.MENDAL@Sierra.Stanford.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Mats_Ohlin_FOA2%QZCOM.MAILNET@MIT-MULTICS.ARPA, ADA_mailing_list%QZCOM.MAILNET@MIT-MULTICS.ARPA
Organization: The ARPA Internet
List-Id: <comp.lang.ada>

This is of good case for arguing that Ada should have (had?)
procedures inside records, much the way SIMULA has.
If so, you could just code E.Delete (or E.Pred.Delete) with
no problems with parameters. It would also given Ada the
possibility to be more "functional". Consider e.g.
a system for matrix handling - a possibility to
code A:= B.Inverse.Transpose; would give much clearer
code than Transpose(A,Invert(B)) with parameters in out.
Something for Ada88 (90?)?

Mats_Ohlin_FOA2%QZCOM.MAILNET [@MULTICS.MIT.EDU]