In a previous post, Automatic Enum Stringification in C via Build-Time Code Generation, I described how to extract enum labels and values directly from DWARF debug information at build time. enum color { C_NONE, C_RED, C_YELLOW, C_GREEN } ; // Request enum descriptor for e_color ENUM_DESCRIBE(e_color, enum color) void foo(enum color c) { printf("Color=%s(%d)\n", ENUM_LABEL_OF(e_color, c), c)
An opinionated list of Python frameworks, libraries, tools, and resources
Modern yazılım geliştirme ekosisteminde altyapının kod olarak yönetilmesi hız ve ölçeklenebilirlik açısından devrim yaratırken GitOps yaklaşımı bu süreci merkezi bir doğruluk kaynağına bağlamaktadır. Ancak tüm yapılandırma detaylarının tek bir platformda toplanması kritik siber güvenlik risklerini de beraberinde getirmektedir. Nesil Teknoloji olarak TSE A Sınıfı sızma testi yetkimizle endüstriyel
Linux kernel source tree
This isn't an anti-Go post. Go is a great language. This is about what I want to understand. I just finished building an L7 HTTP load balancer in Go. It accepts connections. It parses HTTP headers. It forwards requests to backend servers using round-robin. It handles concurrent connections with goroutines. It has health checks. It works. And somewhere in the middle of it working, I realized I didn
Most developers use malloc without thinking much about what happens underneath. This project is an attempt to explore that layer by building a memory allocator from scratch in C. The allocator implements malloc, free, calloc, and realloc without relying on libc’s heap functions. It focuses on: Thread safety Per-thread caching (tcache) Efficient free block management using bins mmap-based memory g
Comments