Mercurial > hg > Members > kono > nitros9-code
comparison docs/ccguide/chain.refentry @ 594:c0da1728ed5b
All refentries finished.
author | roug |
---|---|
date | Fri, 15 Nov 2002 21:49:51 +0000 |
parents | fcb97f0ba24b |
children |
comparison
equal
deleted
inserted
replaced
593:0fda6c7fe48e | 594:c0da1728ed5b |
---|---|
25 </para> | 25 </para> |
26 </refsect1> | 26 </refsect1> |
27 | 27 |
28 <refsect1><title>Description</title> | 28 <refsect1><title>Description</title> |
29 <para> | 29 <para> |
30 Placeholder | 30 The action of F$CHAIN is described fully in the OS-9 |
31 documentation. Chain implements the service request as | |
32 described with one important exception: chain will NEVER return | |
33 to the caller. If there is an error, the process will abort | |
34 and return to its parent process. It might be wise, therefore, | |
35 for the programs to check the existence and access permissions | |
36 of the module before calling chain. Permissions may be checked | |
37 by using "modlink()" or "modload()" followed by an "munlink()". | |
38 </para> | |
39 <para> | |
40 "Modname" should point to the name of the desired module. | |
41 "Paramsize is the length of the parameter string (which should | |
42 normally be terminated with a "\n"), and "paramptr" points to | |
43 the parameter string. "Type" is the module type as found in | |
44 the module header (normally 1: program), and "lang" should | |
45 match the language nibble in the module header (C programs | |
46 have 1 for 6809 machine code here). "Datasize" may be zero, or | |
47 it may contain the number of 256 byte pages to give to the new | |
48 process as initial allocation of data memory. | |
31 </para> | 49 </para> |
32 </refsect1> | 50 </refsect1> |
33 </refentry> | 51 </refentry> |