this post was submitted on 04 Sep 2025

83 points (96.6% liked)

Programmer Humor

26427 readers

401 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 2 years ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

83

a few error handlers from a project im working on (programming.dev)

submitted 2 weeks ago by fmixolydian@programming.dev to c/programmer_humor@programming.dev

7 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Scoopta@programming.dev 6 points 2 weeks ago (1 children)

🤔 that reminds me of the brainfuck debugger I wrote. Good fun

[–] fmixolydian@programming.dev 6 points 2 weeks ago (1 children)

cool! i once tried to write a brainfuck jit compiler (that just appends raw bytes to a buffer and runs it as x86 machine code if it hits a branching instruction like [ / ])

[–] Scoopta@programming.dev 3 points 2 weeks ago (1 children)

That's cool. Mine is just an interpreter for execution but it has breakpoints, watchpoints, and save states. I've thought about trying to do some form of JIT or at least AOT but I haven't yet made an attempt. Besides for a debugger that's counter productive.

[–] fmixolydian@programming.dev 3 points 2 weeks ago

save states are something i've seen very few debugger-enabled interpreters have. on paper, it would probably be as easy as storing the state of the interpreter in a format like a core dump (only requires the ability of reflection)