home *** CD-ROM | disk | FTP | other *** search
- Path: news.nic.surfnet.nl!sun4nl!xs4all!marketgraph!rvg
- From: rvg@marketgraph.xs4all.nl (Ruud van Gaal)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: RunCommand() of "execute" cmd seglist weirdness
- Message-ID: <200cvab60.alamito@marketgraph.xs4all.nl>
- Date: Tue, 2 Jan 96 21:12:32 CET
- Reply-To: rvg@marketgraph.xs4all.nl
- X-Newsreader: Alamito Mail and News Manager (V2.0.4 for Waffle) registered to MARKETGRAPH VISUAL AUTOMATION
-
- In <4c5nra$beq@clare.res.com> samy@res.com (Sam Yee) wrote:
-
- >I used FindSegment() to find the seglist for the command "execute".
- >I have a file called T:runcmd.test, with the content:
- >echo RunCommand begin
- >
- >This is an excerpt of the program:
- >RunCommand(ex_seglist,8192,"T:runcmd.test\n",14);
- >Flush(Output());
- >Printf("RunCommand end\n");
- >exit(0);
- >
- >The output:
- >RunCommand end
- >RunCommand begin
- >
- >This is weird as "execute" is run *after* Printf("RunCommand end\n").
- >This has been confirm with many other batch files such as
- >s:shell-startup. Using RunCommand() on all other commands I've
- >tested has the predictable result.
-
- Are you sure RunCommand() doesn't do something equivalent to 'RUN <program>';
- I mean create
- a new task, and execute it. This way the order of output would be
- unpredictable (which it is).
- Try inserting a Delay(100) command; might change the order around.
-
-
- --
- ---------------------------------
- Ruud van Gaal
- E-Mail: rvg@marketgraph.xs4all.nl
-
-