In PICED, stack use is indicated in the lower left 'Resources' window. Two stats are shown: Min & Max. From what I can tell, these statistics are updated on each scan while logic is running. Given each scan occurs in a fraction of a second, it's kind of difficult to see how close you're sailing to the breeze in terms of memory use. This is because the 'max' stat is just for each current scan. I use quite a few large local variables in functions and procedures, which represent the delta. Some of these functions and procedures are only executed once in a while (like once an hour), and when they do, it's impossible to see how the stack peaks. Wouldn't it be more useful to not reset the 'max' stat every scan? Only time I know when I've got a memory issue is when I get a run-time error... Of course, a bigger stack would help even more! Is it too much to ask for 64k? ;)
