Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site utcsri.UUCP
Path: utzoo!utcsri!gclark
From: gclark@utcsri.UUCP (Graeme Clark)
Newsgroups: net.micro.amiga
Subject: Bug in Manx fexec functions?
Message-ID: <3393@utcsri.UUCP>
Date: Mon, 22-Sep-86 20:13:52 EDT
Article-I.D.: utcsri.3393
Posted: Mon Sep 22 20:13:52 1986
Date-Received: Mon, 22-Sep-86 20:17:10 EDT
Reply-To: gclark@utcsri.UUCP (Graeme Clark)
Organization: CSRI, University of Toronto
Lines: 18
Keywords: Manx Aztec fexecv fexecl
Summary: Has anyone used fexecl and fexecv successfully?

Has anyone successfully used the functions fexecl() and fexecv()
in the Manx (3.20a) library?  When I use them, fexecl() gurus whenever
I call it, and fexecv() does so occasionally.  Is it me?

Can anyone tell me the sequence of operations performed by these
functions so I can write my own version?  It's not sufficient to
just call Execute(); fexec[l|v] allows the child program to be interrupted
with ^C and to inherit the parent's Input() and Output() file handles.
If I had the commercial version of Manx, I'd just look at the source.
However I don't.  Of course posting the source for fexecv() would 
be a copyright infringement, but I'd think posting a summary of the operations
performed by fexecv() would be OK; after all, you can't copyright algorithms,
right?

Thanks for any help you can provide.

Graeme Clark -- Dept. of Computer Science, Univ. of Toronto, Canada M5S 1A4
{allegra,cornell,decvax,ihnp4,linus,utzoo}!utcsri!gclark