Gyeongtae Kim @dev_dasae

Tweets

519
Followers

216
Following

209
Likes

2K

Strace @straceX

6 months ago

x.com/i/article/2017…

99 165 2K 186K 735

View Details

Gyeongtae Kim @dev_dasae

7 months ago

@RLeRoux64 Seen it. Just rooting for them. 👍

1 0 1 21 0

View Details

Modern C is possible. Just quietly dropping this here - my attempt to modernize C with better safety features.😊 (It was supposed to be just a game engine util, but I 'accidentally' spent a year modernize C instead... 😅) github.com/coding-pelican…

2 0 1 302 0

View Details

Gyeongtae Kim @dev_dasae

7 months ago

@Adriksh However, if leveraged correctly, you can achieve a Flutter-like declarative UI syntax in C, just like this.

0 0 2 244 0

View Details

Gyeongtae Kim @dev_dasae

7 months ago

@Adriksh I think it's not a bad idea to use it like below for projects that use old toolchains before and even after the official defer update in GCC and Clang.

0 0 1 2K 2

View Details

Gyeongtae Kim @dev_dasae

7 months ago

@Adriksh There are also extreme attempts like this one to avoid giving up on C at all costs🥹 github.com/coding-pelican…

0 0 3 2K 3

View Details

Gyeongtae Kim @dev_dasae

8 months ago

@gegoxx Zig가 마음에 드셨던 당신! 그런 당신에게 추천드리는 dasae-headers는 어떠신가요! github.com/coding-pelican…

0 0 0 116 0

View Details

Piyush Itankar @_streetdogg

8 months ago

the classic - pass by value and pass by reference example. Given we want to swap the values of x and y. swap(int a, int b); ^^ The value of x and y are passed by copying them to parameter variables that live on the stack. The value is swapped between the parameters. As the function returns, the stack for swap() is destroyed and the original x, y value stay unchanged. swap(int *a, int *b); ^^ a and b are pointers that are fed the addresses of x and y. When swapping, the addresses are used to swap the values. As a result, the values saved at the addresses of x and y are swapped. After the function exits, the value of x and y are seen as swapped (thanks to the address level swap...). Assumptions: 32 bit machine - int is a 4 bytes. - pointers are 4 bytes. --- credits: thanks @bengmugenr for catching the error in previous post.

9 57 425 52K 261

View Details

Gyeongtae Kim @dev_dasae

8 months ago

If you want `.collect()`, you can implement it yourself. 😂 Since I enforce strict zero implicit allocation, you just need to fold the results into your specific container/allocator.

0 0 1 114 0

View Details

Gyeongtae Kim @dev_dasae

8 months ago

This proves that with careful macro design, C can have expressive, functional-style constructs while staying close to the metal. It’s part of my project `dasae-headers`. TestCode: github.com/coding-pelican… Source: github.com/coding-pelican…

1 0 1 175 0

View Details

Gyeongtae Kim @dev_dasae

8 months ago

Rust-style Iterator Chaining in C. One of the goals of my library, `dasae-headers`, is to bring modern ergonomics to C without sacrificing performance. On the left is Rust. On the right is C. The syntax is nearly identical: `filter`, `map`, `reduce` - all implemented via macros with zero implicit allocation.

1 1 9 2K 2

View Details

Gyeongtae Kim @dev_dasae

8 months ago

It is not that I have abandoned macro magic entirely. I simply stopped writing macro sets that act like giant state machine parsers triggered by a single call. I prioritize transparency now. That said, the experience was critical. Understanding how to manually map high-level constructs to bare metal became a massive advantage later in language design and compiler code emission.

0 0 0 49 0

View Details

Gyeongtae Kim @dev_dasae

8 months ago

I absolutely detested having to write new helper macros for every single class definition, or relying on implicit dynamic allocation. My goal was a system that worked universally - whether defined in source files or headers, and regardless of whether the object lived in static memory, the stack, or the heap. I initially held a rigid belief that the syntax "must look like C++." Once I broke free from that obsession, I gained significantly more freedom in designing the syntax and internal structure. The resulting design ended up being much cleaner.

1 0 0 54 0

View Details

Gyeongtae Kim @dev_dasae

8 months ago

Digging up some old C preprocessor "black magic" from my archives. Recently saw a student implementing polymorphic OOP in C macros, and it brought back memories. I used to be obsessed with manually architecting high-level concepts - like Classes and Namespaces - without any implicit allocations in pure C.

1 0 0 83 0

View Details

Gyeongtae Kim @dev_dasae

8 months ago

@RLeRoux64 The name stuck, but the architecture changed! It's not header-only right now (since I decided to make a custom build tool), but returning to a header-only design is quite possible someday

1 0 1 45 0

View Details

Gyeongtae Kim @dev_dasae

8 months ago

@zuhaitz_dev Haha, thanks! Let's make C great again together :D

0 0 0 34 0

View Details

Gyeongtae Kim @dev_dasae

8 months ago

@zuhaitz_dev Oh wow, thanks for the interest! 🙏 (It's my first time sharing about this publicly, so it's exciting yet terrifying 😅) . You can find the repo here: github.com/coding-pelican…

1 0 0 38 0

View Details

Gyeongtae Kim @dev_dasae

8 months ago

@zuhaitz_dev Saw your code and realized we're on the same wavelength! 😯 I'm working on bringing modern features to C as well, specifically Monad-style error handling. I'd love to hear your thoughts on this style: