unhuman Posted January 5, 2011 Share Posted January 5, 2011 Trick ? Are you doing GOSUB without RETURN ? He probably meant GOTO - for counting remaining rams.... Anyhow, Lucien, keep at it, because you're really close. I was about to abandon my game before some of these kind folks shared some techniques (byte-i-fied data statements in strings instead of comma separated numerics) that saved me. There have been some conversations here about how garbage collection slows down string manipulations (I think that qualifier was used) which could be if you're doing TONS. Hopefully I'll get a chance to peek this evening. -H Quote Link to comment Share on other sites More sharing options...
lucien2 Posted January 5, 2011 Author Share Posted January 5, 2011 (edited) Trick ? Are you doing GOSUB without RETURN ? Yes, without return. So it can overflow the stack. There have been some conversations here about how garbage collection slows down string manipulations (I think that qualifier was used) which could be if you're doing TONS. I understand this, but the only string manipulation in each loop was s$=s$+chr$(c) with 3000 bytes of RAM free. In my last exemples I removed all string manipulations in the loop. Edited January 5, 2011 by lucien2 Quote Link to comment Share on other sites More sharing options...
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.