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

Home » Public Forums » archive » SPAWN and reading from a socket?
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: SPAWN [message #8669 is a reply to message #7751] Wed, 09 April 1997 00:00 Go to previous messageGo to previous message
thompson is currently offline  thompson
Messages: 584
Registered: August 1991
Senior Member
Nobuyuki Tasaka <tasaka@mr.med.ge.com> writes:

> Hi all,

> If someone who have tried to compare SPAWN in the following
> usage, please let me know the difference in terms of data
> parsing speed, interface flexibility and routine's independency.

> I would like to use SPAWN for calling database retriving routine
> written in C.

> 1) SPAWN, "cmd", result

> 2) SPAWN, "cmd", /UNIT

This is not a correct usage. The UNIT keyword returns a logical unit number
which can be used to communicate with the spawned process using read and write
commands (via a bi-directional pipe). Thus, one would want to use this with
the syntax:

SPAWN, "cmd", UNIT=UNIT

When one is done, then one can use

FREE_LUN, UNIT

to close the logical unit, since the SPAWN did an implicit GET_LUN.

I've never used this myself, but I would guess that the spawned program would
communicate with IDL using standard input and output.

Another option you haven't discussed is the use of the /NOSHELL keyword with
SPAWN. This is supposed to speed it up.

Bill
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: mswindows postmessage loops?
Next Topic: tiff_read files

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

Current Time: Tue Dec 02 04:22:36 PST 2025

Total time taken to generate the page: 1.86840 seconds