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.7 required=5.0 tests=BAYES_00,INVALID_MSGID,
	REPLYTO_WITHOUT_TO_CC,SUBJ_ALL_CAPS autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII
X-Google-Thread: 103376,409d3c67c89c6b67
X-Google-Attributes: gid103376,public
From: Stephen Leake <Stephen.Leake@gsfc.nasa.gov>
Subject: Re: PARAMETER MISMATCH
Date: 1998/02/17
Message-ID: <34EA06EA.203B@gsfc.nasa.gov>#1/1
X-Deja-AN: 325999829
Content-Transfer-Encoding: quoted-printable
References: <34E9D6D3.6396@er.uqma.ca>
Content-Type: text/plain; charset=iso-8859-1
Organization: NASA Goddard Space Flight Center -- Greenbelt, Maryland USA
Mime-Version: 1.0
Reply-To: Stephen.Leake@gsfc.nasa.gov
Newsgroups: comp.lang.ada
Date: 1998-02-17T00:00:00+00:00
List-Id: <comp.lang.ada>


jj091849@er.uqma.ca wrote:
I remember enough high school french to understand your post; hope you
can understand my response!
> =

> Bonjour j'ai une petit programme qui a une erreur de
> parameter mismatch =E0 la lige 49
> getelem (elem,s_elem,aut_elem,ref_elem :OUT string);

you are calling "getelem" with only 4 parameters; you declare it with
six parameters:

> =

> PROCEDURE getelem (ka: In natural;
>                 str1 :In string;
>                 elem,s_elem,aut_elem,ref_elem :OUT string) IS


One way to get better error messages from the compiler (at least with
GNAT and ObjectAda) is to use named parameter calls:

getelem =

	(elem =3D> elem,
	 s_elem =3D> s_elem,
	 aut_elem =3D> aut_elem,
	 ref_elem =3D> ref_elem);

then the compiler will give an error message listing the missing
parameters.

-- =

- Stephe