Open lemanschik opened 1 year ago
Stealify Lang Implements also VFS Interfaces to the lowest Level Of the Kernel Interfaces see: VFS minimal-boot
remember: vfs is not a userland thing this is the kernel vfs that implements read, open, write, close the kernel syscalls
The below shows how to create memory save modules via c++ bindings directly into our engine. This is How we make rust obsolete. And C++ Memory Save as it runs in our VM with the Memory it gets assigned to which again allows you and your company to reuse your existing C++ Codebases and still be compliant to the US Advice to use Memory Safe Languages over c++.
Stealify Lang is Also Fundamental Memory Safe as it Builds Every Module in its own Virtual Machine and then links the memory parts via handlers that are needed the security concepts and garanties of capability based protocols. It Implements by design a declarative in memory wire layout that is readable and understandable composed out of simple modules written in any language.
Example blake 3 Module with bindings.
The below is a hand written raw module example only to illustrate the C++ Template Function pattern and to show a reusable example how to apply it to common c++ module like blake3 to create directly built In Engine bindings for it.
blake3.cc
blake3.h
What does the above give us is relative clear for a c++ 20 programmer. It will link properties and functions into a context that it gets as parameter. That will produce a context with that builtIn Functions that is later link able into our VM directly via creating a new context out of that which we can use like it would be nativ build in while this is fully Modular Load Able by the engine.
This pattern is n times faster then ffi or other methods it is modular and still as fast and sometimes even faster as a nativ build in module or component.
for the geeks this is what the compiler will do on the low level as Makefile syntax to be more understandable