theKernel 10.0
Loading...
Searching...
No Matches
Topics | Namespaces
MK_CC_API

The CcMkKernel API. More...

+ Collaboration diagram for MK_CC_API:

Topics

 MkKernel_CC_API
 MkKernel PACKAGE - The package is the toplevel structure of the Programming-Language-Micro-Kernel (PLMK) …
 
 MkRuntimeC_CC_API
 MkRuntimeC - The class known as mkrt or runtime is the main ccmkkernel application environment …
 
 MkObjectC_CC_API
 MkObjectC - class known as obj or object is used as base-class type for a Programming-Language-Micro-Kernel (PLMK) class …
 
 MkBufferC_CC_API
 MkBufferC - the abstract class known as buf or buffer is used to create and manage dynamic, generic, mixed typed data. …
 
 MkBufferStreamC_CC_API
 MkBufferStreamC - the abstract class known as bus or stream is a subclass of MkBufferC and is used for package-based-io …
 
 MkBufferListC_CC_API
 MkBufferListC - the class known as bfl or buffer-list is used to create and manage a list of MkBufferC …
 
 MkLogFileC_CC_API
 MkLogFileC - the class known as lfl or log-file is used to control the target of the logging-output …
 
 MkErrorC_CC_API
 MkErrorC - the class known as err or error is used to create and manage an error message …
 
 MkExceptionC_CC_API
 MkExceptionC - the final class to connect the MkErrorC with the C++ error …
 

Namespaces

namespace  ccmkkernel
 namespace for the CcMkKernel "C++"-API
 

macros to support types

#define MqTypeCC_O   MK_BOL
 
#define MqTypeCC_Y   MK_I8
 
#define MqTypeCC_S   MK_I16
 
#define MqTypeCC_I   MK_I32
 
#define MqTypeCC_W   MK_I64
 
#define MqTypeCC_F   MK_FLT
 
#define MqTypeCC_D   MK_DBL
 
#define MqTypeCC_C   MK_STRN
 
#define MqTypeCC_B   MK_BNP
 
#define MqTypeCC_U   MkBufferC*
 
#define MqTypeCC_US   MkBufferStreamC*
 
#define MqTypeCC_L   MkBufferListC*
 

Detailed Description

The CcMkKernel API.

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 ccmkkernel. 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 (ccmkkernel),
  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 ccmkkernel library and is responsible for the quality-target of the entire project.
  • implementation of the managed-object technology
  • 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.
Target
!! This documentation describe the implementation-layer and target the C++ programmer. !!

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 ccmkkernel. 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 (ccmkkernel),
  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 ccmkkernel library and is responsible for the quality-target of the entire project.
  • implementation of the managed-object technology
  • 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.
Target
!! This documentation describe the implementation-layer and target the C++ programmer. !!

Macro Definition Documentation

◆ MqTypeCC_B

#define MqTypeCC_B   MK_BNP

Definition at line 184 of file LibMkKernel_cc.hh.

◆ MqTypeCC_C

#define MqTypeCC_C   MK_STRN

Definition at line 183 of file LibMkKernel_cc.hh.

◆ MqTypeCC_D

#define MqTypeCC_D   MK_DBL

Definition at line 182 of file LibMkKernel_cc.hh.

◆ MqTypeCC_F

#define MqTypeCC_F   MK_FLT

Definition at line 181 of file LibMkKernel_cc.hh.

◆ MqTypeCC_I

#define MqTypeCC_I   MK_I32

Definition at line 179 of file LibMkKernel_cc.hh.

◆ MqTypeCC_L

#define MqTypeCC_L   MkBufferListC*

Definition at line 187 of file LibMkKernel_cc.hh.

◆ MqTypeCC_O

#define MqTypeCC_O   MK_BOL

Definition at line 176 of file LibMkKernel_cc.hh.

◆ MqTypeCC_S

#define MqTypeCC_S   MK_I16

Definition at line 178 of file LibMkKernel_cc.hh.

◆ MqTypeCC_U

#define MqTypeCC_U   MkBufferC*

Definition at line 185 of file LibMkKernel_cc.hh.

◆ MqTypeCC_US

#define MqTypeCC_US   MkBufferStreamC*

Definition at line 186 of file LibMkKernel_cc.hh.

◆ MqTypeCC_W

#define MqTypeCC_W   MK_I64

Definition at line 180 of file LibMkKernel_cc.hh.

◆ MqTypeCC_Y

#define MqTypeCC_Y   MK_I8

Definition at line 177 of file LibMkKernel_cc.hh.

Generated on Thu May 29 2025 13:13:26 for theKernel by doxygen 1.12.0