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,ef6c792702c0ff46
X-Google-Attributes: gid103376,public
From: Al Johnston <sofeise@mindspring.com>
Subject: Re: ada to c interfaces and CHARS_PTR
Date: 2000/03/10
Message-ID: <38C91E2D.99FC13E1@mindspring.com>#1/1
X-Deja-AN: 595733640
Content-Transfer-Encoding: 7bit
References: <38C7E515.29C42580@mindspring.com>
 <LN%x4.491$34.9257@news.swbell.net>
X-Accept-Language: en
X-Server-Date: 10 Mar 2000 16:11:20 GMT
Content-Type: text/plain; charset=us-ascii
Organization: MindSpring Enterprises
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 2000-03-10T16:11:20+00:00
List-Id: <comp.lang.ada>

> If it dies when it tries to do a subroutine return, perhaps the
> calling conventions don't match?

I think they did... the problem was I screwing up the
"body" of my c program (c codeing goof)

> Also, what does strdup do?  If
>   *inout_strg_fml = strdup(t_buffer);

strdup(3c) allocates new memory and copies the supplied
string to it.  It doesnt go away until a free(3c) is called. And
yes.. I know the program has 2 leaks in it.

thanks for the assistance... but my real problem was that
I didn't pay enough attention to my c code...

-al