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,8e64f4db20d57eb5
X-Google-Attributes: gid103376,public
From: Karl Cooper {46901} <ktc@swl.msd.ray.com>
Subject: Re: Call by reference vs. call by value
Date: 1996/07/22
Message-ID: <31F39035.41C67EA6@swl.msd.ray.com>#1/1
X-Deja-AN: 169482649
references: <31F10E50.726@egr.uri.edu> <dewar.837901109@schonberg>
content-type: text/plain; charset=us-ascii
organization: Raytheon Electronic Systems
mime-version: 1.0
newsgroups: comp.lang.ada
x-mailer: Mozilla 2.0 (X11; I; SunOS 4.1.4 sun4m)
Date: 1996-07-22T00:00:00+00:00
List-Id: <comp.lang.ada>


Robert Dewar wrote:

> P.P.S. In C++ you can't pass arrays anyway so the issue does not arise, so it
> is wrong to say that the mechanism for this is defined in C++! If you cold
> pass arrays in C or C++, then the same problem would arise.

This is really a C or C++ issue, but I still am not sure I understand.  I seem
to remember passing arrays as function parameters in both C and C++.  Since an
array reference is always implemented with a pointer in C and C++, all such
passing is pass by reference.  Why then do you say you can't pass arrays anyway?