going slightly mad. Old code is fine, new is borked. These buffers are never freed (just left for OS to clean up when program exits).
anyone?
| C64 scene | https://csdb.dk/scener/?id=8958 |
| bsky | https://bsky.app/profile/shrydar.bsky.social |
Christopher
@shrydar
- 85 Followers
- 129 Following
- 353 Posts
4th Doctor, Python, 6502, Rust, C64. Hair dye and heels, code optimisation and data compression. Former Driv{e3}r2?/Stuntman dev. he/him
Maybe I should get an external monitor at work sometime that's a bit bigger than the 13" screen on my laptop? Or just some more sleep, this size of text is usually fine.
So good getting an in-editor warning on this one. I think I was already going to add the parens myself this time (I'd just added the mask a moment earlier), but it's definitely caught me out in the past.
(thanks to JetBrains, curses to K&R. Comparisons should have been between & and &&, wtf guys)
(thanks to JetBrains, curses to K&R. Comparisons should have been between & and &&, wtf guys)
Sometimes Christopher can write a little hot garbage, as a treat.
(don't do this)
Haha oops.
Asm breakpoint is at exit from 6502 version of getBitPair(ctx), with Y=ctx. Python reference implementation log shows decoder calling getBitPair with values of 0x20, 0x30, 0x10, asm shows calls with 0x20, 0x30, 0x0a (i.e. 10 decimal)
#c64 #compression #6502
