QuoteBegin-Insanity+9 Apr, 2007, 20:5-->QUOTE (Insanity @ 9 Apr, 2007, 20:50) |
Even ASM? What about crashes? That's a lot of archive writes to have to back up every time before you test out a change to your program... (correct me if I'm wrong) |
*ESPECIALLY* ASM programs. Besides, the reasonable things you'd be editing would be numerical boundries and such. The chances of causing a crash if you're aware of what you are doing are small if you know you're doing something that won't cause such a thing. Now, if you were doing something that you know might cause a problem, then I can see where you're getting at.
But the kind of editing that I normally do are safe. If I do something that crashes the calc, then I know the next time I go back to the computer to make a certain change. You see, the most valuable aspect of debugging an ASM program is to make sure that the calc crashes if anything goes wrong. If it doesn't crash, then the programmer remains oblivious to any potential problems that may be experienced.
QuoteBegin-calc84maniac+10 Apr, 2007, 7:28-->QUOTE (calc84maniac @ 10 Apr, 2007, 7:28) |
I use Omnicalc's Ram Recovery so I don't have to archive everything. :) |
There will soon be a program that'll compete with the same RAM space that Omnicalc uses for RAM Recovery. But that's on a different topic.
I also use Calcsys to inspect memory addresses and areas around where a utility should've edited. I do this so that variables unreadable in the BASIC editor would be readable through this. I mean, I do want to make sure that what I wrote creates and edits in the proper fashion. This also helps in debugging.