Chapter Contents |
Previous |
Next |
Coprocessing Functions |
costart
. However, each coprocess' stack space
is expanded dynamically as necessary.
=minimal
run-time
option or its compile-time equivalent) in an application that uses coprocesses.
quiet
function in
one coprocess has no effect on diagnostic messages generated by another.
exit
function, the
entire program is terminated.
The details of program termination are described in Advanced Topics: Program Termination. A call to
coexit
in the main coprocess is treated as a
call to
exit
.
longjmp
cannot be used to transfer control between coprocesses. In particular,
you cannot call
setjmp
in one coprocess and call
longjmp
using the same
jmp_buf
in another. Any attempt to do this causes abnormal program termination.
malloc
is shared by all
coprocesses. Memory allocated by one coprocess
can be freed by another. Similarly, load modules loaded by one process can
be used or unloaded by another, and files opened by one coprocess can be used
or closed by another.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.