Is being delivered in service packs on NetWare as far back as NetWare 4.11. Is the basis for many libraries on NetWare in that it furnishes a great number of common interfaces
KLib provides them at this lower level for consumption by low-level code as well as applications. They are well-suited to drivers, stacks, libraries, and other low-level code. Consequently, KLib interfaces are completely reentrant and thread-safe. KLib interfaces act only upon input parameters and, when making use of global or other data not passed in through the interface (an example is _ctype), treat such data as read-only. In any case, the furnished functionality has no obligation to library concepts of thread binding, context, and ownership. The K in KLib stands for kernel because these functions might have been provided and consumed at that level. KLib is implemented by KLib.NLM and supplies interfaces which were once the domain of CLib to NLM developers that don't want to load atop CLib. This article covers a new runtime library, KLib, in use on the NetWare operating system. Debugging and Functions Called from KLib, CLib, and LibC.
KLIB ROSEVILLE HOW TO
How to Write Drivers and Other Components to KLib instead of CLib.
In this AppNote, we will elaborate on this new library and discuss development-related issues and techniques that leave the domain of application programming (based on CLib or NKS/LibC) and enter the domain of code that is properly thought of as kernel-level.
0 kommentar(er)
