0 Members and 7 Guests are viewing this topic.
input acts funnily...prgmBASIC[code=BASIC]Input "THE GAME: ",A
input
Yes - garbage collecting seems to work wonders. I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.
Quote from: Michael_LeeYes - garbage collecting seems to work wonders. I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.But even if it does work, you should probably report your "mysterious error." Might be a bug in Axe.
Well apparently the buffer where the input string is stored is not a temporary variable so a bcall to _CleanAll doesn't clear it. I will have to find the name of that string. The buffer for the input is named "-" and I've seen a "#" and "$" so I'm guessing it's something similar to that.There isn't a way to fix the memory leaks since this is an OS call.
Quote from: Deep Thought on September 20, 2010, 10:56:33 amQuote from: Michael_LeeYes - garbage collecting seems to work wonders. I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.But even if it does work, you should probably report your "mysterious error." Might be a bug in Axe.I doubt it. The 'mysterious errors' usually only occur after I try running a normal, tested program after doing something incredibly stupid with my calculator. (As in, I mess up with pointers and accidentally write a bunch of data to random places). It's probably not Axe's fault.
Quote from: Quigibo on September 19, 2010, 05:54:16 pmWell apparently the buffer where the input string is stored is not a temporary variable so a bcall to _CleanAll doesn't clear it. I will have to find the name of that string. The buffer for the input is named "-" and I've seen a "#" and "$" so I'm guessing it's something similar to that.There isn't a way to fix the memory leaks since this is an OS call.As you are probably aware, there is a leak-free (or less so) version of _GetKey, undocumented and called _GetKeyRetOff I wonder if something similar exists for the input bcall...Good luck making it work!
Quote from: Michael_Lee on September 20, 2010, 01:57:54 pmQuote from: Deep Thought on September 20, 2010, 10:56:33 amQuote from: Michael_LeeYes - garbage collecting seems to work wonders. I find that whenever I get a mysterious error that never happened before, garbage collecting usually clears things up.But even if it does work, you should probably report your "mysterious error." Might be a bug in Axe.I doubt it. The 'mysterious errors' usually only occur after I try running a normal, tested program after doing something incredibly stupid with my calculator. (As in, I mess up with pointers and accidentally write a bunch of data to random places). It's probably not Axe's fault.Ah. Yeah, I accidentally do that pretty often, giving me random tokens in the middle of my program