Sander in 't Veld
Sander in 't Veld
As far as I understand, there is an important difference between `traceUtf8` and `textUtf8`. The former outputs text to the console, which expects a UTF8 encoded string. The latter draws...
Oh you are totally right. In fact I myself mentioned using ```Rust text(unsafe { std::str::from_utf8_unchecked(&[0x80]) }, 20, 20); ``` in Rust as a workaround for this bug, which (besides being...
I've started working on a fix (https://github.com/aduros/wasm4/pull/528) for the web runtime. It still requires a solution for backwards compatibility and a port to the native runtime, but I wanted to...
> Note that by deprecating, I mean removing it from headers and printing a warning in the console when it is imported, but still keeping the implementations for as long...
I've implemented backwards compatibility and ported it to the native runtime. I'm not familiar enough with WebAssembly to figure out how to actually make the old functions deprecated. A `trace`...
I finished updating the templates and the documentation. I was a bit confused by the mismatched function declarations in the Go and Odin templates, and I wasn't able to test...
I completely agree! WASM-4 should not support Unicode characters beyond U+00FF. Maybe my test images were a bit confusing. Despite the name, this issue is not about extending/changing the encoding...
Not quite. ASCII treats each byte (0x00 through 0xFF) as a single character, and the 224 characters supported by the WASM-4 font are 0x20 (space) through 0xFF (y with dots),...
It would affect all existing carts written in Zig, Rust, Go and Odin that drew any characters above 0x7f. Those characters become question marks.
Given that #591 solves the main functionality problem (allowing Rust developers to draw `"\x80"` without UB), and does not suffer the loss of ergonomics that I was afraid of (because...