Might be a matter of knowing the right design patterns etc.
I found Deep C Secrets quite helpful
Guile has GOOPS. Racket is probably better suited for game dev and has Swindle but it doesn't seem to be well-documented.
You'd think Deep C-crets or something like that would have been a slam dunk but what do I know
Dependency injection is the best anti-debugger technique you can get without resorting to tricks with inline assembler and IRQ hooks.
Dependency injection forces or at the very least encourages SOLID. It's hard to fuck up the rest of your program if you write tests while developing at that point.
Petition to make it common practice to name all C variables after sea creatures. I will confess I’ve named a few of my (basic) c programs after sea puns like csick.
Yeah, I've messed with GOOPS before, it's nice.
Apparently Racket has a very decent cross-platform GUI library and, for something as sophisticated as a GUI library, I would imagine most other standard libraries are cross-platform, with obvious exceptions like Unix sockets. Perhaps you can learn Swindle with prior exposure to CLOS and GOOPS.
There are definitely subtleties like array decay.
Guile can also cause some pretty nasty problems due to its design on the low level. For example if you embed Guile you'd better be sure your host application's runtime doesn't ever setjmp, because Guile sure does and relies on longjmp to handle things like continuations.
Yeah, there are definitely options. It's mostly just a lack of time, what with work and whatnot.
Oh weird. I wouldn't have thought that necessary considering guile is a bytecode implementation.
I'm just smart enough to vaguely understand this. Certainly not smart enough to implement it.
Where do you learn stuff like this?
Usually by running into the issue and tearing your hair out for five hours.
In short, from seeing Guile put in places it probably doesn't belong. Exceptions and Smart Pointers both usually rely on longjmp. Guile of course supplies scm_throw and garbage collection so freestanding programs have to go out of their way to run into any ugliness. Though, the moment you want to play around with Scheme in an engine or framework that provides its own memory management and error handling they will step on each other's toes and you absolutely will throw exceptions into a continuation, catch exceptions that were never thrown and dereference prematurely free'd resources.
I more so meant more specifically what leads you to embed Guile or anything like it in a C application so that you reach that point. But other than that yeah I am ready to mald:
Have you had any experience with embedding Lua? A lot of people seem to have a high opinion of it in that context.
Aside from troubleshooting, a lot of my low-level knowledge comes from poking around in disassemblers and debuggers. Reverse engineering firmware for embedded devices and malware (if you're super careful about it) can teach you a lot of little esoteric tidbits and tricks used to implement certain features. You get to see a lot of that classic human ingenuity that has sadly been dying off and obscured with the rise of black box silicon chips that last a year or two at most.
For me, this can usually be summed up quite nicely by a classic Portal 2 quote:
Cave Johnson said:
Personally a little experience. The main reason why its spoken highly of is it was (successfully) designed with that specific purpose in mind,
Don't we all? I'd assume it's almost a universal experience.
I mean, yeah, it was meant as a conversation starter about what kind of language
