Cesare Nanni Costa<a href="https://pixelfed.uno/discover/tags/c?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#c</a>'eraunavolta<br>
<a href="https://pixelfed.uno/discover/tags/onceuponatime?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#onceuponatime</a>
#c
19 posts14 participants0 posts today
In honour of the Amiga's birthday, I'm starting something I always wanted to do: an Amiga game in C. It's been decades since I used C in any meaningful way, and I never used it on the Amiga. Should be fun... 
I feel like raylib is a good cross platform gui and game engine.
* Things I don't care about:
"native look and feel" I could not care less about this kind of thing.
* Things I DO care about:
Using opengl when most/all of my ideas are 2D. (I don't like it.)
But ... I also like ncurses for simple stuff. So this is the compromise.
GUIs get OpenGL and TUIs (ncurses) are for the retro/old/remote machines.
Otherwise, I can't find a decent C gui lib. GTK is too big and I don't like constant
version churn. (basically that is ALL the gui libs.)
Lot's of the simpler stuff I find is wrappers for something bigger like gtk.
If I wasn't so into #C and #OpenBSD right now, I would probably just be happy
to use tcl/tk for gui stuff.
#GUI #TUI #C
#raylib
* Things I don't care about:
"native look and feel" I could not care less about this kind of thing.
* Things I DO care about:
Using opengl when most/all of my ideas are 2D. (I don't like it.)
But ... I also like ncurses for simple stuff. So this is the compromise.
GUIs get OpenGL and TUIs (ncurses) are for the retro/old/remote machines.
Otherwise, I can't find a decent C gui lib. GTK is too big and I don't like constant
version churn. (basically that is ALL the gui libs.)
Lot's of the simpler stuff I find is wrappers for something bigger like gtk.
If I wasn't so into #C and #OpenBSD right now, I would probably just be happy
to use tcl/tk for gui stuff.
#GUI #TUI #C
#raylib
Far and away
#Leica #Leica M6 #M6 #Kodak #Vision3 #Vision3 500T #500T #C-41 #analog #shootfilm #film #photography #BelieveInFilm
#Leica #Leica M6 #M6 #Kodak #Vision3 #Vision3 500T #500T #C-41 #analog #shootfilm #film #photography #BelieveInFilm
Continued thread
I favor the less latter, but I am only seeing the former in OpenBSD code.
So I think I might default to using the former.
To be clear that means in a function definitions add
parans and the asterisk to a function pointer name: int (*fnptr)(int)
as opposed to: int fnptr(int)
They both work, and I am guessing the latter is like a newer
convieniance. (totally guessing)
The declarations have a similiar nuance:
void fn(int (*)(int));
vs.
void fn(int * int);
I think I have also only seen the former in OpenBSD code so far.
In my example I didn't type out the whole definition stanza, but I did
I did type out the whole declaration.
#C #OpenBSD
So I think I might default to using the former.
To be clear that means in a function definitions add
parans and the asterisk to a function pointer name: int (*fnptr)(int)
as opposed to: int fnptr(int)
They both work, and I am guessing the latter is like a newer
convieniance. (totally guessing)
The declarations have a similiar nuance:
void fn(int (*)(int));
vs.
void fn(int * int);
I think I have also only seen the former in OpenBSD code so far.
In my example I didn't type out the whole definition stanza, but I did
I did type out the whole declaration.
#C #OpenBSD
https://codeberg.org/pkw/learn/src/branch/main/fun_ptr.c
in C. Both function definitions seem valid. I like the top
one, but see things more like the bottom in OpenBSD code.
I was looking in tmux code. (random grepping)
I wouldn't mind seeing better examples of passing function
pointer as parameters.
It doesn't say anything about them in style. [0]
But the lead i buried is that I really like them. I thought they
were more convoluted. They do break the indent program. [1]
[0]: https://man.openbsd.org/style
[1]: https://man.openbsd.org/indent
Until now I have been running indent on all my C code all the time.
#C #OpenBSD
I'm playing with function pointers as parameters
void
fun_ptr_test1(void (*f1) (char *), void (*f2) (char *))
{
f1("v1...");
f2("v2...");
}
int
fun_ptr_add_results(int f1(int), int f2(int))
{
return f1(10) + f2(20);
}
/* the style difference is in the declaration *.h file too */
in C. Both function definitions seem valid. I like the top
one, but see things more like the bottom in OpenBSD code.
I was looking in tmux code. (random grepping)
I wouldn't mind seeing better examples of passing function
pointer as parameters.
It doesn't say anything about them in style. [0]
But the lead i buried is that I really like them. I thought they
were more convoluted. They do break the indent program. [1]
[0]: https://man.openbsd.org/style
[1]: https://man.openbsd.org/indent
Until now I have been running indent on all my C code all the time.
#C #OpenBSD
Codeberg.orglearn/fun_ptr.c at mainlearn - Examples in C to learn.
I like to think of Arch Linux in the same way the C programming language gives you the freedom to royally screw things up if you don't know what you're doing, and NixOS in the same way that the Rust programming language provides safety to prevent you from easily making stupid mistakes.
Title: CnCNet
️ What's: A libre tool that simplifies SP/MP play with the old free C&C titles
️ https://cncnet.org/
️ https://github.com/cncnet
#LinuxGaming #ShareYourGames #RTS #C&C
️ #LibreEngine #FreeAssets #Arch #RPM #Deb
️ https://lebottinlinux.vps.a-lec.org/LO.html
️ Update: 2.12.7
Minor vers. 
️
️
️️
️ Changes: https://github.com/CnCNet/xna-cncnet-client/releases
️ From: 
️ https://github.com/CnCNet/xna-cncnet-client/releases.atom
https://www.youtube.com/embed/4Qse4t_jDxY
️ https://www.youtube.com/embed/rkQPh-HoNVQ️ https://www.youtube.com/embed/Kb4yis-45LU?start=1108️ https://www.youtube.com/embed/_8lN4NhW5Lg