# Home
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 %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://camelot-1.gitbook.io/docs/home.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.