MK_PY_API

The LibMkKernel API … More...

Collaboration diagram for MK_PY_API:

Topics
	MkKernel_PY_API
	MkKernel PACKAGE - The package is the toplevel structure of the Programming-Language-Micro-Kernel (PLMK) …
	MkObjectC_PY_API
	MkObjectC - class known as obj or object is used as base-class type for a Programming-Language-Micro-Kernel (PLMK) class …
	MkBufferC_PY_API
	MkBufferC - the abstract class known as buf or buffer is used to create and manage dynamic, generic, mixed typed data. …
	MkBufferStreamC_PY_API
	MkBufferStreamC - the abstract class known as bus or stream is a subclass of MkBufferC and is used for package-based-io …
	MkBufferListC_PY_API
	MkBufferListC - the class known as bfl or buffer-list is used to create and manage a list of MkBufferC …
	MkLogFileC_PY_API
	MkLogFileC - the class known as lfl or log-file is used to control the target of the logging-output …
	MkErrorC_PY_API
	MkErrorC - the class known as err or error is used to create and manage an error message …
	MkExceptionC_PY_API
	MkExceptionC - The default-exception of the Programming-Language-Micro-Kernel (PLMK) …
	MkRuntimeC_PY_API
	MkRuntimeC - The class known as mkrt or runtime is the main pymkkernel application environment …

Detailed Description

The LibMkKernel API …

Unlocking the Power of C Across All Languages: Discover theKernel

The world of software development often faces a fundamental challenge: harnessing the unparalleled performance and vast ecosystem of C libraries while building applications in modern, higher-level programming languages. Traditionally, this requires creating complex, language-specific bindings for each library and each target language.

But what if there was a way to bridge this gap seamlessly, enabling you to

Write Once → Run Everywhere ?

Enter theKernel, a revolutionary infrastructure designed to provide a programming-language-independent-interface between a C librarie and a multitude of Target-Programming-Language (TPL). At its core lies the Programming-Language-Micro-Kernel (PLMK), implemented primarily by the C library pymkkernel. This isn't just another binding generator; it's a comprehensive system that defines an object-layer and manages the interaction between your robust C code and diverse language environments.

The strategic approach is described as taking

4 years to write a programming-language, but it only takes 4 weeks to insert a micro-kernel.

The magic happens through a sophisticated object-interface and an api-layer automatically generated by the meta-code-compiler (META-COMPILER).

PROGRAMMING

This structure is clearly defined by separating concerns into three distinct programming layers:

1. the library-layer (pymkkernel),
2. the tool-layer (theCompiler and build tools),
3. the target-layer (the API seen by the Target-Programming-Language (TPL) programmer).

library-layer

The library-layer implement the pymkkernel library and is responsible for the quality-target of the entire project.

• implementation of the managed-object technology
  • providing basic classes for: buffer, list, stream, logging, runtime and error
• establishing and managing the library-items
  • providing the startup and cleanup API
  • providing the logging, debugging and error API
  • providing the memory and garbage-collection API
• written in plain C

tool-layer

The tool-layer creates the tools and is responsible for the integration of all components into the NHI1 framework.

• implementation of the project and build technology.
• implementation of the token-stream-compiler technology
• generate the source-code for the target-layer.
• written in plain C, TCL and the Target-Programming-Language (TPL)

target-layer

The target-layer is the API used by the target-language-programmer.

• written in plain Target-Programming-Language (TPL)

Target

!! This documentation describe the implementation-layer and target the Python programmer. !!