Feoramund (@feoramund) 's Twitter Profile
Feoramund

@feoramund

Contributor to the Odin programming language.

ID: 1779393238446563328

linkhttps://github.com/Feoramund calendar_today14-04-2024 06:16:29

373 Tweet

120 Takipçi

12 Takip Edilen

Feoramund (@feoramund) 's Twitter Profile Photo

You collapse the superposition of possible solutions by observing one already made and constrain your future timeline to a less novel outcome. You can always go back and look at someone else's solution afterwards. You can never get back the novelty of the first, uninformed try.

Feoramund (@feoramund) 's Twitter Profile Photo

I like how C89 needs all variable declarations to be written at the top of a scope. Even better is to put all of them at the top of a function. This way, it is easy to get a feel for the stack memory requirement of the function, as it mirrors what happens in the assembly.

Feoramund (@feoramund) 's Twitter Profile Photo

There are times when I need to know what macros a C compiler has defined by default. This can be useful for learning information not otherwise known in the available set of standard C headers.

There are times when I need to know what macros a C compiler has defined by default.

This can be useful for learning information not otherwise known in the available set of standard C headers.
Feoramund (@feoramund) 's Twitter Profile Photo

"When it looks elegant because it magically solves your problem, that means your bugs are also magical." There's also a compelling argument against ZII in this talk around the 15 minute mark: initialize memory such that the program will crash if it's not set correctly.

Feoramund (@feoramund) 's Twitter Profile Photo

If you were stuck on a desert island and you could only choose one type of integer: signed or unsigned, which would it be? RobertElderSoftware explores this question here: blog.robertelder.org/signed-or-unsi…

If you were stuck on a desert island and you could only choose one type of integer: signed or unsigned, which would it be?

<a href="/RobertElderSoft/">RobertElderSoftware</a> explores this question here: blog.robertelder.org/signed-or-unsi…
Feoramund (@feoramund) 's Twitter Profile Photo

The latest video by Eskil Steenberg covers how to catch and even log these memory mistakes, in C, using a clever allocator interface that you can build yourself. youtube.com/watch?v=sfrnU3…

Feoramund (@feoramund) 's Twitter Profile Photo

A benchmark report from Dr. Dobb's Journal, August 1986 shows that there were no less than twelve C compilers at this point in history, 14 years after C's inception. C had not even been standardized yet.

A benchmark report from Dr. Dobb's Journal, August 1986 shows that there were no less than twelve C compilers at this point in history, 14 years after C's inception.

C had not even been standardized yet.
Feoramund (@feoramund) 's Twitter Profile Photo

There are no synchronization primitives in C89, you say? Here, look, a simple mutex in half a page of x86-64 assembly that can be called with ease; now you have mutexes in C89.

There are no synchronization primitives in C89, you say?

Here, look, a simple mutex in half a page of x86-64 assembly that can be called with ease; now you have mutexes in C89.