comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » CALL_EXTERNAL and IDL_STRING
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: CALL_EXTERNAL and IDL_STRING [message #23119 is a reply to message #22931] Wed, 03 January 2001 21:00 Go to previous message
Mark Rivers is currently offline  Mark Rivers
Messages: 49
Registered: February 2000
Member
Frederique Soulard wrote in message
<91vttb$tpn$1@s1.read.news.oleane.net>...
> We are trying to use the CALL_EXTERNAL function in order to get strings
from
> a C routine. The variables are defined as IDL_STRING and have to be
> modifyable into the C routine. Our C routine reads strings from a binary
> file into C string variables. Then we are trying to copy the C strings into
> the IDL_STRING pointers (copy byte after byte). We encounter problems while
> doing this (memory overlaping probably). Does someone has any advice to
give
> in order to solve our problems (no question to re-develop the reading in
IDL
> routine) ? Is a ByteArr method a solution ?


Yes, I always use byte arrays for this. In IDL dimension your byte arrays
so that the dimension
which is the string length is greater than it will ever need to be in the C
code. Have the C code
fill in the byte array with trailing NULLs. On return to IDL convert to a
string or string array using the string() function.

Mark Rivers
[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: Re: IDL 5.3, Trouble with Laptop under Linux, using TrueColor
Next Topic: Re: I for Interactive Programming? (was: widget_control and group_leader)

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu Oct 09 17:27:22 PDT 2025

Total time taken to generate the page: 1.12139 seconds