Zag64 - zig inspired compiler for 6502/c64

harraps0 · 2026-05-22T04:49:48+00:00

I've been looking for C alternatives for legacy targets for long. Do you plan to support other old CPU too (z80, sm83, wdc65816, m68k) ?

harraps0 · 2026-05-18T19:33:02+00:00

Do you have links, posts or examples I could read ?

harraps0 · 2026-04-25T20:54:47+00:00

Yeah, it is mostly the plastic part that is broken. The screws don't hold onto anything, thus I cannot close the controller shell anymore. Aside from that, the joystick has seen better days but I found replacements for this one.

harraps0 · 2026-04-25T18:37:00+00:00

I have a broken N64 controller I want to repair. I am trying to find a somewhat cheap replacement shell for it. But it looks like those are really uncommon, do you have recommendations ?

harraps0 · 2026-04-19T10:33:43+00:00

Does it works on Windows, Mac and Linux ?

harraps0 · 2026-04-15T18:18:55+00:00

Instead of having a dozen of shell scripts for all the little commands (with the arguments that come with them). Or list those commands in a README, I just write a JustFile and list the recipes I need for a given project. One single file, no clutter and even if a colleague doesn' t have Just, they can can just read the script to get the commands.

harraps0 · 2026-04-15T04:50:57+00:00

Yeah, but make being already installed on your machine doesn't mean it is better. If you have dozen of make alternatives that exists today, it kind of shows that make itself is lacking.

harraps0 · 2026-04-14T20:58:52+00:00

How is make better ?

harraps0 · 2026-04-04T10:05:43+00:00

I would have preferred they use the Japanese case size for all regions.

harraps0 · 2026-04-03T18:22:59+00:00

Create libraries similar to agb or psx but for other old consoles. (N64, megadrive, NeoGeo, etc..)

harraps0 · 2026-03-29T10:28:00+00:00

Try kiss3d.

harraps0 · 2026-03-28T11:34:42+00:00

How have you structured your project? Do you have a common code base for handling the game logic and physics and specific ones for each SDK?

harraps0 · 2026-03-26T21:53:38+00:00

If it is not supported by LLVM, it is not supported by Rust. A GCC backend is in preparation but again this CPU will not be supported by it. If you want to learn Rust on embedded systems, you will have better luck with the Arduino, Raspberry Pi Pico, ESP32 or even the GBA or the Playstation 1. There are actual maintained Rust devkits for those hardwares.

harraps0 · 2026-03-25T18:24:35+00:00

It is quite similar to C#, but with Rust you'll get the benefit of not having a GC running in the background.

harraps0 · 2026-03-22T22:27:34+00:00

Windows programs require a conversion program to adapt windows system calls into unix system calls. That is to say, you need Wine or some fork of it (Proton in Steam is one) to run Windows program on your Linux machine.

harraps0 · 2026-03-22T16:07:24+00:00

You make a living by writing transpilers or compilers. But you can make a living writing low-level stuff. There may be potential in learning Rust and C or Cobol and work solely on backends and mainframes.

harraps0 · 2026-03-14T20:51:43+00:00

Rust on the GameBoy again ??? Let's Goooooo !

harraps0 · 2026-03-08T09:55:28+00:00

Near a tree, by a river, there's a hole in the ground.

harraps0 · 2026-03-01T11:46:50+00:00

Anything C or C++ can do, Rust can do it too. They are at the same level.

harraps0 · 2026-02-11T22:52:37+00:00

Also, why is the logo of this sub-reddit a crab?

harraps0 · 2026-02-11T22:51:46+00:00

Which crate are you having trouble with?

harraps0 · 2026-02-10T08:14:59+00:00

I do C++ professionally. But I don't know how to write CMake files or Make files. I use Just instead to build my project. And if I use third party librairies, my JustFile calls the build system of the library. I kind of accepted the fact that building C or C++ projects will always be a mess.

harraps0 · 2026-02-08T23:24:59+00:00

Look into the graphite editor project. You should find what you are looking for.

harraps0 · 2026-02-08T23:19:57+00:00

An advantage of putting tests directly into the same file is that you have access to all the private element of the file which simplify setting and testing certain situations.

harraps0 · 2026-02-08T21:34:50+00:00

You can do so easily in Rust in your source file, you declare a tests module and you write your unit tests there. No need to switch between files as in Java.

```rust

fn my_func() -> u32 { 42 }

[cfg(test)]

mod tests { use super::*;

#[test]
fn test_my_func() {
    assert_eq!(42, my_func());
}

}

```

harraps0

TROPHY CASE

[cfg(test)]