ekipan

How about reusing `_` for ignored parameters? @Avokadoen's code would look like: ```zig fn messageCallback( _: vk.DebugUtilsMessageSeverityFlagsEXT.IntType, // message_severity _: vk.DebugUtilsMessageTypeFlagsEXT.IntType, // message_types p_callback_data: *const vk.DebugUtilsMessengerCallbackDataEXT, _: *c_void, // p_user_data...

@emekoi I found out after posting that your suggestion was already proposed and rejected: https://github.com/ziglang/zig/issues/9239#issuecomment-868783930. In that proposal fengb mentioned using just `_` but dismissed it because it hides intent....

Likewise, on Windows XP 32-bit, the official RetroArch Phoenix 0.9.9 crashed for me but the one I built goes without issue. Could I ask you to upload a debug build...

I've mentioned before that durexForth is my first time touching the C64. I've never written any programs that touch the disk yet, but in the Forth spirit of keeping things...

I'm working on this "simplest" thing right now, [a `block` with a single buffer](https://gist.github.com/ekipan/5691d14c17aed55041bdb4a2fb68e494). I _think_ it's debugged now? Scratching files in VICE is sometimes flaky for me when I'm...

About that. I might have written one ([z: a block editor](https://gist.github.com/ekipan/28bb4bd609797b6d85c58af45d14ed61)) as an exercise to see if I could, over the last week. It's not quite as small as you...

Though now I want to write one without any interactivity at all, just commands at the interpreter using the C64 screen editor. I'm sure it'll be a lot smaller. It...

Well, I think I wrote it. Less than 400 bytes compiled :tada:. ```forth require block marker -- \ -tt-- create scr 1 , : edit dup scr ! block drop...

The interpreter's ok prompt does like to overwrite line numbers. I could `at-xy` after an `rr` but that's also slightly inconvenient to use, having to cursor back to where you...

I'm still noodling around with `z`, I'll never be satisfied with good enough. Latest revision just now is at least copypasted from the C64 so I know it compiles.