Closed patricksurry closed 4 months ago
I'll try to check this out this weekend. I've been using c65 for testing and it is orders of magnitude faster. This wasn't an issue I was particularly worried about, as Tali will never generate these on its own, but it's nice to know it is taken care of. Is this something worth passing upstream?
that's a good point, i'll also make a PR against the upstream where I found that include. no idea if it's still active
On Wed, Apr 24, 2024 at 9:18 AM SamCoVT @.***> wrote:
I'll try to check this out this weekend. I've been using c65 for testing and it is orders of magnitude faster. This wasn't an issue I was particularly worried about, as Tali will never generate these on its own, but it's nice to know it is taken care of. Is this something worth passing upstream?
— Reply to this email directly, view it on GitHub https://github.com/SamCoVT/TaliForth2/pull/71#issuecomment-2074929533, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABA5MKTXREPFBTC3TSW2LADY66WJJAVCNFSM6AAAAABGSSNHK2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZUHEZDSNJTGM . You are receiving this because you authored the thread.Message ID: @.***>
The upstream https://github.com/C-Chads/MyLittle6502 is archived as read-only, but I pushed the change and a link to taliforth/c65 to my own fork. So there are a few breadcrumbs if someone is looking.
Fix and tests for #65