""My work building TrapC has taken two parallel paths," Rowe explains in his initial post. "A TrapC interpreter called itrapc and a separate compiler called trapc. I had wanted to make a software release by 1 January 2026, but too many bugs. I only reached code complete this month and am now on the painstaking and sleepless process of debugging. When I have something stable that mostly works I will make a release. Sorry to make you wait a little longer. Aiming for Q1 2026.""
"Memory safety provides a way of ensuring that memory-related bugs like out-of-bounds reads/writes and use-after-free don't happen. In large codebases, like Chromium and Windows, most of the security vulnerabilities follow from memory bugs. As that message has been repeated in recent years, memory safety has become an imperative, evangelized by the likes of Google and Microsoft, and more recently by authorities in the US and elsewhere."
TrapC is a memory-safe version of the C programming language nearing test readiness. Development includes an interpreter named itrapc and a separate compiler named trapc. The project reached code complete this month, but active debugging continues with a target release in Q1 2026. Memory safety prevents out-of-bounds reads and writes and use-after-free vulnerabilities that cause most security issues in large codebases. Public and private sectors are promoting memory-safe development, encouraging migration from C/C++ to safer languages like C#, Go, Java, Python, Swift, and Rust. C and C++ communities are adapting to remain relevant.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]