memory leak proof every C program
Memory leaks have plagued C programs for as long as the language has existed. Many solutions have been proposed, even going so far as to suggest we should rewrite C programs in other languages. But there’s a better way. Presented here is a simple solution that will eliminate the memory leaks from every C program. Link this into your program, and memory leaks are a thing of the past. leakproof.c#in
www which wasm works
We’ve gotten libjxl built for wasm. It was a struggle, but we got it done, and we’re ready to run it. WASM is a straightforward standard designed for ease of implementation, so this should be a walk in the park. wazeroLet’s start with wazero: the zero dependency WebAssembly runtime for Go developers. “Import wazero and extend your Go application with code written in any language!” The initial down
a brief history of one line fixes
Apple recently made a booboo, unlike any other booboo in the history of programming. Even though Apple’s bug is unprecedented, here’s a brief overview of some predecessor bugs. XBack in 2006, the X server checked to make sure the user was root, but forgot to actually call the function. --- hw/xfree86/common/xf86Init.c +++ hw/xfree86/common/xf86Init.c @@ -1677,7 +1677,7 @@ } if (!strcmp(argv[i], "-
the three line single binary compiler free blog
A silly experiment that quickly ended up deep in the rabbit hole. The new hotness is a single binary blog, with all the posts embedded inside. There’s a few approaches people have used to get the posts included into the final executable, but they all involve recompiling. Who has a compiler? That’s so insecure. Hackers use compilers. Let’s build a blog that doesn’t require recompiling everything ju
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
fixing the other go loop bug
banging errors in go
honk 1.0
azorius 0.1
warning: implicit backdoor
