Toby Ewing wrote:
Two questions:
- Why didn't the program crash when doing the assignments? It crashed
on the write loop, but not on the previous loop. Aren't both accessing illegal memory?
Maybe, depends on the system what is in this memory. For me it crashes while or after freeing memory, maybe because some memory manager data structures were corrupted ...
- (only distantly related) when I change the loop counter from Integer
to Card, I get a compiler warning for every loop, something like 'condition is always "True"'. What is this about?
This would be a GPC bug. I can't reproduce it, please send a test case.
Frank also noted:
But you don't actually have to, since using a schema type is not only easier and avoids the difficult size and index computations, but also avoids the upper limit.
I mentioned this is a previous email. Briefly, I need to be able to walk through the cube, one layer at a time, and move information to another cube. I don't have enough memory for both cubes, so I have to be able to peel more dynamically.
Well, then a schema array of pointers to another schema array, no problem. :-)
Frank