It's sad that old programming languages are not widely known enough on stack-exchange. So no one is able to answer these particular questions. I believe it would be a great feature for this site if we had "retro-coding" questions.


So I was wondering if its on topic on this site to ask about coding on retro-computers?


I think we should allow programming questions, if we are programming on something which is on-topic for this site. For example, 6502 is on-topic here, so 6502 assembler programming is. Same with PDP-11 or Z80. Not so with ARM7 or x86.

I suppose if your question is about the BASIC in your random home computer's ROM, it's on topic, but not if your question is that elementary and easily googlable. For example: "What is a for loop?" would be off-topic, but Why does this BASIC program keep restarting? is on-topic.

Programming in something like C could be on topic if:

  • it's specifically something about not-modern C, like "what is this weird pre-K&R syntax and what does it mean?" Or, "Why doesn't this old compiler accept this perfectly valid syntax?"

  • it's something specific to a retro system. So you just happen to be using C, but the question is really about how the Terak's framebuffer is laid out, or what escape codes the ADM-33 expects.

  • It's something we don't often [need to] think about today, but could rear its head on an exotic architecture. Something like "Why is a pointer to a byte a different size from a function pointer?" or "This array doesn't seem to occupy contiguous memory, what's up with that".

If your question is about VBA, then you can sod off, we're not interested. If your question is about Haskell or Python, then still it's off-topic but we'll be nicer about it.

If your question is really about implementation details of some programming language feature on some old platform, or the history of some language or language feature, then we'll welcome that kind of question.


Niche retro programming questions are on-topic, as per Are x86 programming questions on-topic?. Ordinary programming questions belong on Stack Overflow, and programming challenges belong on Code Golf.

I don't think we should allow programming questions, unless they require domain knowledge. So, debugging this timing loop is only on-topic if the timing loop is failing for a weird reason, like the graphics chip stealing RAM access, and not for mundane reasons like the program counter (instruction pointer) accidentally being used as a general-purpose register.

  • Depends on the type of program counter: A Z80 PC is fine, even if mis-used, ARM or x86 probably not. – tofro Aug 22 at 17:41
  • @tofro I'm not sure that the issue I described is possible to accidentally create in Z80 assembly. – wizzwizz4 Aug 22 at 18:20
  • PUSH <reg16>; RET; Does exactly what you're talking about – tofro Aug 23 at 9:05

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .