> For the complete documentation index, see [llms.txt](https://camelot-1.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://camelot-1.gitbook.io/docs/home.md).
# Home
Welcome to your team’s developer platform
C23 WITHOUT THE FOOT-GUNS
The modern standard library for architectural rigor. No malloc. No printf. No undefined behavior. Just strict, deterministic systems engineering.
Documentation GitHub
{% columns %}
{% column %}
**❌ The Legacy Way**
```c
void legacy_main() {
char *name = malloc(1024); // Heap allocation?
printf("Name: ");
scanf("%s", name); // Buffer overflow risk
// Forgot to free(name) -> Memory Leak
}
```
{% endcolumn %}
{% column %}
**✅ The Camelot Standard**
```c
#include
void main() {
// 1. RAII Workspace (Auto-free)
Workspace ctx = arena.create(1024);
// 2. Buffer-Safe Input (Slice)
io.print("Name: ");
String name = io.scan(&ctx, 0);
// 3. Type-Safe Output
io.print("Hello, %S\n", name);
} // Memory released automatically here.
```
{% endcolumn %}
{% endcolumns %}
Philosophy
| |
|---|
| Memory Sovereignty | We replace manual free() with Linear Allocators (Arenas). All memory belongs to a scoped Workspace. When the scope ends, the memory vanishes. Mathematically leak-proof. |
| String Theory | Camelot Strings are Slices (ptr + len). They know their own size. Substring operations are O(1). Buffer overflows are structurally impossible. |
| Ecosystem Interoperability | Full extern "C" linkage guards allow Camelot to function as a static library within C++ engines. |
Statistics
{% columns %}
{% column %}
0 Dependencies
{% endcolumn %}
{% column %}
<1s Compile Time
{% endcolumn %}
{% column %}
100% Static Analysis Pass
{% endcolumn %}
{% column %}
ASC-1.3 Strict Contribution Standard
{% endcolumn %}
{% endcolumns %}
