u/NightOwlDev
Why I Still Reach for Lisp and Scheme Instead of Haskell
Lisp (and Scheme) allows you to express complex systems and problem domains in more simple terms than any other language can. For all its brilliance, Haskell resists most of the attempts people make to just hack and write useful code quickly.
TIL that the standard library provides support for complex numbers
Accessible via the `complex.h` header What other useless things have you encountered in C?
Getting Formatting Errors Loading .C Files in Turbo C for DOS
I am having a problem with loading .c files in ye olde Borland Turbo C for DOS 2.01. .C files will display properly if I load them in any other editor on earth, under any other operating system, but Turbo C seems to ignore line feeds(?) when loading that same file into it's IDE editor. It will throw out an error about the line being too long, etc. Sincerely, Getting a Bit Annoyed in Bermuda Edit: Thanks all for your input. I found that if I loaded the file into an editor that would format it properly and then resaved it was fixed Cheers!
Good afternoon, folks
Hey, I’m NightOwlDev. I started with C and still use it when I want to understand what’s happening close to the machine. These days I also write Rust for side projects, mostly small CLI tools and experiments with networking. I’m interested in low-level programming, Linux, debugging, and the kind of bugs that only show up late at night.
Async/Await in C?
The question explains itself, but for context: I am writing an Over-Engineered HTTP server for fun's and learning's sake, and I have hit a conceptual roadblock. Currently, the server works thusly: One (1) thread sits on a port and accept()s incoming requests and adds them to a queue, then pthread_cond_signal()s a condition that... ... Four (4) threads (request handlers) are pthread_cond_wait()ing on, one of whom will pick up the request and parse it. Here comes the issue: Similar to that the server simply adds each request to a queue, I want each request handler to, once it's parsed a request, hand it off to some HTTP_<method> function, then pick up the next request from the queue, only returning to the original point of execution (the point where HTTP_<method> was called), where it then returns a response. The only two ways that comes to mind of doing this, one of them require N more threads sitting on another queue, which I feel weird about, and the other requires some Macro Fuckery that I found on a Github repository then lost, so Idk if it even is feasible. How do I go forward from here? TL;DR: Async Await for C; good, bad, or disgustingly ugly? Potential other solutions?