summaryrefslogtreecommitdiffhomepage
path: root/source/wg01
diff options
context:
space:
mode:
authorAmlal El Mahrouss <amlal@nekernel.org>2025-12-22 16:19:07 +0100
committerAmlal El Mahrouss <amlal@nekernel.org>2025-12-22 16:19:07 +0100
commit600cc0b1a0ef68c1b5ea7417846ffb5fa8dcf6e9 (patch)
tree093b7c35ef15ca3d6484e385effa366111b87298 /source/wg01
parent78f751eaa4473bd97b4133d268361ae7c20fb5d6 (diff)
fix: Better writting and document improvements.
Signed-off-by: Amlal El Mahrouss <amlal@nekernel.org>
Diffstat (limited to 'source/wg01')
-rw-r--r--source/wg01/wg01.tex9
1 files changed, 4 insertions, 5 deletions
diff --git a/source/wg01/wg01.tex b/source/wg01/wg01.tex
index f52154d..0f1e45c 100644
--- a/source/wg01/wg01.tex
+++ b/source/wg01/wg01.tex
@@ -144,7 +144,7 @@ If two of the three conditions fail, then the framework fails, and you should co
\subsection{V: Compile-Time Vetting in a Freestanding Domain.}
-The following concept makes sure that the `class T' is vetted by the domain. Such properties are called `Vettable' such program in the domain makes sure that a `Container' is truly deemed fit for a Run-Time or Compile-Time Evaluation Domain. The `IVettable' structure makes use of template meta-programming in C++ to evaluate whether a `Container' shall be vetted, such containers inherit the `IVettable' structure and are marked final. Such system may look like this in a Compile-Time Evaluation Domain:
+The following concept makes sure that the `class T' is vetted by the domain. Such properties are called `Vettable' such program in the domain makes sure that a `Container' is truly deemed fit for a Run-Time or Compile-Time Evaluation Domain. The `Vettable' structure makes use of template meta-programming in C++ to evaluate whether a `Container' shall be vetted. Such system may look as such in a Compile-Time Evaluation Domain:
\begin{lstlisting}
#define NE_VETTABLE static constexpr BOOL kVettable = YES;
@@ -171,11 +171,10 @@ if constexpr (IsVettable<UnVettable>) {
} else {
instVet->Abort();
}
-\end{lstlisting} Source: \href{https://github.com/nekernel-org/nekernel/blob/develop/src/kernel/NeKit/Vettable.h}{Link}. \\Note: This is one approach to compile time vetting, one may solve this using tags instead of a base `IVettable' class.
+\end{lstlisting} Source: \href{https://github.com/nekernel-org/nekernel/blob/develop/src/kernel/NeKit/Vettable.h}{Link}.
-\section{Conclusion}
-{ Safe and correct development in a freestanding domain is indeed possible granted the above concepts are applied and respected. A reference implementation of this paper exists, It's called NeKernel.org, available under the same internet address.
-}
+\section{VI: Conclusion}
+{ Safe and correct development in a freestanding domain is indeed possible granted the above concepts are applied and respected.
\section{References}