A stopgap for this - what if save() checked how many variables were in use and refused to save() if more than 3040 were in use? That way, we could use more at runtime, as long as we didn't try to save more than we could fit. I mean 4860-3040 is only 1620 jsvars, and if you have a program that saved requires 3000 jsvars, realistically when you run it, you're gonna need another 500-1500 jsvars anyway...
Also, crud, builds for picoram aren't being created. I think I forgot to have the script delete the old build directory. Maybe it's failing because i'm not getting all the locks off the directory - this byzantine process where you actually have to change directory to the git repo to make it get the branch instead of the trunk and working with that garbage seems to keep tripping me up. It doesn't help that it takes like 20-30 mins to test the script.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
A stopgap for this - what if save() checked how many variables were in use and refused to save() if more than 3040 were in use? That way, we could use more at runtime, as long as we didn't try to save more than we could fit. I mean 4860-3040 is only 1620 jsvars, and if you have a program that saved requires 3000 jsvars, realistically when you run it, you're gonna need another 500-1500 jsvars anyway...
Also, crud, builds for picoram aren't being created. I think I forgot to have the script delete the old build directory. Maybe it's failing because i'm not getting all the locks off the directory - this byzantine process where you actually have to change directory to the git repo to make it get the branch instead of the trunk and working with that garbage seems to keep tripping me up. It doesn't help that it takes like 20-30 mins to test the script.
Edit: nvm - just no version bump so far.