KwikNet Low Level Services
K
DAK
145
KwikNet
Procedure Descriptions
A description of all KwikNet low level service procedures is provided in this chapter. The
descriptions are ordered alphabetically for easy reference. All of the KwikNet procedures
are described using the C programming language.
Italics are used to distinguish programming examples. Procedure names and variable
names which appear in narrative text are also displayed in italics. Occasionally a lower
case procedure name or variable name may appear capitalized if it occurs as the first
word in a sentence.
Vertical ellipses are used in program examples to indicate that a portion of the program
code is missing. Most frequently this will occur in examples where fragments of
application dependent code are missing.
:
: /* Continue processing */
:
Capitals are used for all defined KwikNet filenames, constants and error codes. All
KwikNet procedure, structure and constant names can be readily identified according to
the nomenclature introduced in Chapter 1.3.
A consistent style has been adopted for the description of the KwikNet procedures
presented in Chapters 4.6 and 5.4. The procedure name is presented at the extreme top
right and left as in a dictionary. This method of presentation has been chosen to make it
easy to find procedures since they are ordered alphabetically.
Purpose A one-line statement of purpose is always provided.
Used by n Task o ISP o Timer Procedure o Restart Procedure o Exit Procedure
This block is used to indicate which application procedures can call the
KwikNet procedure. A filled in box indicates that the procedure is allowed
to call the
KwikNet procedure. In the above example, only tasks would be
allowed to call the procedure.
For AMX users, this block is used to indicate which of your AMX
application procedures can call the
KwikNet procedure. You are reminded
that the term ISP refers to the Interrupt Handler of a conforming ISP.
...more
Comments to this Manuals