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,fcbc5bb7c18362e0
X-Google-Attributes: gid103376,public
From: Tucker Taft <stt@averstar.com>
Subject: Re: HELP: Interfaces.C...
Date: 2000/04/11
Message-ID: <38F389B6.E078A42C@averstar.com>#1/1
X-Deja-AN: 609797377
Content-Transfer-Encoding: 7bit
References: <8cipco$prq@r02n01.cac.psu.edu>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@inmet2.burl.averstar.com
X-Trace: inmet2.burl.averstar.com 955484598 10333 141.199.8.164 (11 Apr 2000
 20:23:18 GMT)
Organization: AverStar (formerly Intermetrics)  Burlington, MA  USA
Mime-Version: 1.0
NNTP-Posting-Date: 11 Apr 2000 20:23:18 GMT
Newsgroups: comp.lang.ada
Date: 2000-04-11T20:23:18+00:00
List-Id: <comp.lang.ada>

"Jack W. Sharer" wrote:
> ...
> While this code works, the form of the first and second
> arguments appear to go against the spirit of the
> Interfaces.C... packages.

I think your first solution is fine.  Using 'Access to pass
array parameters should be a last resort.  It is used by
some automatic binding generators, because they don't know
whether a given pointer argument in C is really an IN, IN OUT, or
OUT parameter.  Since you are creating this binding by hand,
use all the information you can to minimize the use of access
types.

> ...
> Could you help me get into the Interfaces.C... spirit?

Stick with your first solution.  It was in the "Ada" spirit,
which is more important, IMHO.  Furthermore, it works!

> 
> Thanks,

-- 
-Tucker Taft   stt@averstar.com   http://www.averstar.com/~stt/
Technical Director, Distributed IT Solutions  (www.averstar.com/tools)
AverStar (formerly Intermetrics, Inc.)   Burlington, MA  USA