zirk.us is one of the many independent Mastodon servers you can use to participate in the fediverse.
Literature, philosophy, film, music, culture, politics, history, architecture: join the circus of the arts and humanities! For readers, writers, academics or anyone wanting to follow the conversation.

Administered by:

Server stats:

753
active users

#c

78 posts74 participants13 posts today

On a #coding mission to improve my #poser lib 😎.

In the current implementation of #swad, I don't really like that I need an extra thread, just to control a child #process. A first piece to add to poser is generic "child process support", which I'm testing right now. I realized I could reuse my #Connection class, which was built for #sockets, but works just as well with #pipes 🙃

TODO now is mostly testing. See screenshots for some mimimal testing code and its output ... would you like this kind of interface? 🤔

Hey guys, I'm studying #computersci
#ComSci

So far I've ben learning about #python and soon going to do #c soon.
Would people benefit from me posting about what I've learned? I'm assuming not, after-all, there's lot of documentation online and Mastodon isn't a documentation site, obviously.
Ultimately I'd like to connect in some way with learners/the programming community out there on the fediverse!
One reason why I've been thinking about posting what I've learned is: I really, really hated programming for the first and most of the second semesters of college,I struggled to understand concepts, but suddenly one day it clicked that actually, I do love making programs and this isn't actually so hard!
Don't give up people! Programming is a rough ride for the first while, but it's well worth it and eventually you'll experience that wow/feeling of inspiration moment. Work is hard, but it does pay off in the longterm.

Still working on #swad, and currently very busy with improving quality, most of the actual work done inside my #poser library.

After finally supporting #kqueue and #epoll, I now integrated #xxhash to completely replace my previous stupid and naive hashing. I also added a more involved #dictionary class as an alternative to the already existing #hashtable. While the hashtable's size must be pre-configured and collissions are only ever resolved by storing linked lists, the new dictionary dynamically nests multiple hashtables (using different bits of a single hash value). I hope to achieve acceptable scaling while maintaining also acceptable memory overhead that way ...

#swad already uses both container classes as appropriate.

Next I'll probably revisit poser's #threadpool. I think I could replace #pthread condition variables by "simple" #semaphores, which should also reduce overhead ...

github.com/Zirias/swad