Lines Matching refs:in
7 Guidelines for writing \f5ksh-93\fP built-in commands
14 is the ability to add built-in commands at run time.
22 that can be loaded into \f5ksh\fP at run time as built-in
26 A built-in command is executed without creating a separate process.
28 If this function has no side effects in the shell process,
29 then the behavior of this built-in is identical to that of
31 in this case is performance. The overhead of process creation
35 about 50 times faster as a built-in command.
37 In addition, built-in commands may have side effects on the
43 result in a windowing shell that can be used to write
46 While there are definite advantages to adding built-in
48 Since the built-in command and \f5ksh\fP share the same
49 address space, a coding error in the built-in program
57 Resources used by a built-in must be meticulously maintained and freed.
58 Also, since the address space of \f5ksh\fP will be larger when built-in are loaded,
60 exec() non-built-in commands.
61 It makes no sense to add a built-in command that takes
64 Built-ins that have side effects in the current shell
66 coupling between the built-in and \f5ksh\fP, making
69 Despite these drawbacks, in many cases extending
70 \f5ksh\fP by adding built-in
72 scripting ability in an application specific domain.
108 The AST Toolkit also contains some examples of built-in libraries under
114 of the built-in you wish to define.
115 A built-in command has a calling convention similar to
120 \f5Shbltin_t*\fP is in \f5<ast/shcmd.h>\fP.
124 The \f5open\fP built-in, installed in \f5lib/ksh\fP in the AST Toolkit, uses this method.
143 of the built-in source file, where \fIidentifier\fP is any C identifier.
145 that it uses to verify compatibility between the built-in and \f5ksh\fP
148 date and requires an upgrade or the built-in is out of date and requires
151 The steps necessary to create and add a run time built-in are
152 illustrated in the following simple example.
153 Suppose you wish to add a built-in command named \f5hello\fP
155 by its argument. First, write the following program in the file
178 and run \f5nmake install\fP to compile, link, and install the built-in shared library
179 in \f5lib/ksh/\fP under \f5PACKAGE_ast\fP.
180 If the built-in extension uses several \f5.c\fP files, list all of these on
198 The final step is using the built-in.
201 and add the built-in \f5hello\fP, invoke the command,
208 If you install the shared library in \f5lib/ksh/\fP, where \f5../lib/ksh/\fP is
213 will automatically find, load and install the built-in on any system.
219 It is often desirable to make a command \fIbuilt-in\fP
222 whereas for subsequent invocations \f5ksh\fP should just execute the built-in.
233 This file \f5hello\fP needs to be placed in a directory that is
234 in your \fB\s-1FPATH\s+1\fP variable, and the built-in shared library
235 should be installed in \f5lib/ksh/\fP, as described above.
249 \f5#define\fP constants in \f5ksh\fP interface
255 The header files in the development kit are compatible with
301 Programs that want to use the information in \f5<sys/stat.h>\fP
318 I/O library defined in ANSI-C.
327 The man page for the \f5sfio\fP library is in an Appendix.
330 performance improvements in \f5sfio\fP
341 in future versions of \f5ksh\fP.
344 \f5errormsg()\fP specifies the dictionary in which the string
369 The first thing that a built-in should do is to check
392 In fact a complete man page in \f5troff\fP or \f5html\fP
459 It is important that any memory used by your built-in
460 be returned. Otherwise, if your built-in is called frequently,
463 be freed before returning from you built-in, because by default,
464 \f5ksh\fP will terminate you built-in in the event of an
469 which is included in \fBlibast\fP
477 in the Appendix.
479 Before \f5ksh\fP calls each built-in command, it saves
483 location in the \f5b_\fP entry function,
486 The following coding convention will do this in
504 the functionality of \f5ksh\fP in application specific directions.
517 A man page for this file is provided in an Appendix.
519 to access the functions defined in the \fBnval\fP library.
522 Each shell variable is an object in an associative table
551 is used in interpreting the second argument.
620 that can also be called from built-in commands.
621 The man page for these routines are in the Appendix.
624 builtin commands. It takes the name of the built-in, the
625 address of the function that implements the built-in, and
628 If the function address is \f5NULL\fP, the specified built-in
629 will be deleted. However, special built-in functions cannot
636 of the shell built-in \f5printf\fP command.