Airshack Posted January 18, 2017 Share Posted January 18, 2017 (edited) Today i ran into some memory issues on a program for XB/XB256 so it looks like I'm going to have to go back and re-write some code. I tried using XBasher yet it crashed maybe because it didn't like the XB256 code? Anyway, I'm re-writing now and wondering if the TI Faithful have tip such as: >>> Don't use CALL CLEAR because DISPLAY ERASE ALL saves 5 bytes. <===== Who knew? I use two-character variable names so there's not much there to save memory.. How about multiple commands on the same line? Is the limit 256 characters? Any tips you share are appreciated. - James Edited January 18, 2017 by Airshack Quote Link to comment Share on other sites More sharing options...
Retrospect Posted January 18, 2017 Share Posted January 18, 2017 Today i ran into some memory issues on a program for XB/XB256 so it looks like I'm going to have to go back and re-write some code. I tried using XBasher yet it crashed maybe because it didn't like the XB256 code? Anyway, I'm re-writing now and wondering if the TI Faithful have tip such as: >>> Don't use CALL CLEAR because DISPLAY ERASE ALL saves 5 bytes. <===== Who knew? I use two-character variable names so there's not much there to save memory.. How about multiple commands on the same line? Is the limit 256 characters? Any tips you share are appreciated. - James If you give some examples of your code, I'm sure someone will point out things that can be done using less bytes. Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.