Toby Ewing wrote:
Finally got it.
In the end the problem wasn't in the list work at all. Way earlier in the program, I'd allocated memory for an array [1..x], then accessed it as [0..x]. On freeing the memory, I guess something funny was set up in the memory manager that came back to bite me way later.
So... is there a compiler option I could have set that would have told me about this illegal memory access?
_No array index checking_ in gpc up to now unfortunately
Franck,
You have said some time ago that check of array addresses was not so important ...
You said also in an other mail that you were not fond of numeric analysis ...
The two are closely related because this kind of lost of days of time is by far the most important for anybody who does numeric analysis programs...
Correcting this is in my opinion the most urgent thing to do after the 2.1 release.
Maurice