Lines Matching refs:built
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.
29 then the behavior of this built-in is identical to that of
35 about 50 times faster as a built-in command.
37 In addition, built-in commands may have side effects on the
41 built-ins that make heavy use of the shell variable namespace.
42 These built-ins are added at run time and
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
66 coupling between the built-in and \f5ksh\fP, making
70 \f5ksh\fP by adding built-in
76 built-ins as part of the AST (AT&T Software Technology) Toolkit.
84 for functions that you can call from built-ins. The \f5lib\fP
92 utilities that can be made run time built-ins.
94 that implement other \f5ksh\fP built-ins.
101 To add built-ins at runtime, it is necessary to build a shared library
102 containing one or more built-ins that you wish to add.
103 The built-ins are then added by running \f5builtin \-f\fP \fIshared_lib\fP.
108 The AST Toolkit also contains some examples of built-in libraries under
111 There are two ways to code adding built-ins. One method is to replace
114 of the built-in you wish to define.
115 A built-in command has a calling convention similar to
124 The \f5open\fP built-in, installed in \f5lib/ksh\fP in the AST Toolkit, uses this method.
135 use the \f5Shbltin_t.shbltin()\fP function to add one or more built-ins.
139 The \f5dbm_t\fP and \f5dss\fP shell built-ins use this method.
141 No matter which way you add built-ins you should add the line
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
153 Suppose you wish to add a built-in command named \f5hello\fP
178 and run \f5nmake install\fP to compile, link, and install the built-in shared library
180 If the built-in extension uses several \f5.c\fP files, list all of these on
195 If you have several built-ins, it is desirable
198 The final step is using the built-in.
201 and add the built-in \f5hello\fP, invoke the command,
213 will automatically find, load and install the built-in on any system.
216 If you are using \f5lib_init\fP method to add built-ins then no arguments
222 whereas for subsequent invocations \f5ksh\fP should just execute the built-in.
234 in your \fB\s-1FPATH\s+1\fP variable, and the built-in shared library
237 As mentioned above, the entry point for built-ins must either be of
240 Your built-ins can call functions from the standard C library,
369 The first thing that a built-in should do is to check
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
479 Before \f5ksh\fP calls each built-in command, it saves
620 that can also be called from built-in commands.
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.