You know, I wish #C compilers had a super strict warning compiler flag, I know there's -Wall, but it doesn't actually turn on all warnings oddly enough.
C could probably be almost as safe as memory-safe languages if the programmer didn't have to pass 30 different warning flags, link with ASAN and UBsan, pass mysterious -f compiler flags, pass odd macro flags like _D_FORTIFY_SOURCE, etc.
You know, doing Object-like programming in #C does feel a bit wrong. But I can't deny it makes the code cleaner to look at!
Macro functions in #C makes manipulating strings just a bit more tolerable lol
So, i'm making a library of functions that I constantly re-create for my #C programs. I'm calling it #libcharadon (creative, I know), and it has no dependencies and is written in gnu99 standard.
No repo for it yet, but I'm wanting to make it easy to add as a submodule for #meson projects.
Sneak peak of my sh2exe program in action ;)
Welp, I've tested on most platforms, and my Pong game works perfectly. So I'm probably gonna release v1.0 today, and finally move on from this spaghetti code of a project lmao
It has been tested and works for: #Linux #Windows #Mac #NetBSD #OpenBSD #FreeBSD #Solaris #Illumos #OpenIndiana
It probably works on #DragonflyBSD and #MidnightBSD too.
It'll be published here: https://www.opencode.net/charadon/Pong-C
#bsd #gamedev #foss #linuxgaming #bsdgaming #raylib #sdl #C #Pong
I've been busy today for the most part, but I managed to squeeze in a little bit of #rust practice.
- I did some fiddling around with println
- Used cargo for a bit, and like it. But seriously, vendor your dependencies people...
- Messed around with threading and atomics, works a lot like how SDL abstracts it on #C
@mo8it@fosstodon.org Maybe. I do like how simple #C is though, I make mostly non-security critical applications (Games, basic non-internet connected applications, etc), so I never really have to worry about security, therefore I can do some funky shit in C lmao
I love #C, but strings make me want to die sometimes...