Raven, so it could well be just my interpretation of what the memory usage is. I am aware of most of the memory management functions under the Windows Kernel but the obvious (Chewing) of memory when running me program is worrying if I can't trace where the leak is occurring.
I did sort out the labelling and varariable assignment, took me an hour or so to sift through the code checking every single function and found a couple of potential smackers, but the memory usage is still there. I'm stumpped as to where it's getting used.
I stuck SECTION_analysis functions on all include modules that used arrays and they all contained legitimate count values depending on their usage, yet this 32k paging problem just chewed up the memory every couple of seconds. I've not left the program running long enough to see exactly what happens when the memory usage hits maximum, probably throw up (Low resources) error or something and completely splat the OS or max out the swap file but I need to test this incase it is just a rougue memory usage value being displayed.
The last thing I need is to release my program onto the Internet community, only to find that it chews up their memory and swap file space!! lol. Best put a clause or disclaimer in there I think.
Anyway, back to my last posting. Labels should definately be localised to the function scope (Although the editor could actually check this before compiling, depending on which IDE is in use) And an Option explicit, again could be checked by the editor if it handled the DB syntax correctly.
And, ON ERROR, now I agree that this is a BASIC concept, so exception handling (Try, Catch and Throw) is probably too advanced for the scope of DarkBASIC as an error handling system and this would need some form of exception object handling that Cattle pointed out. But ON ERROR is a good start.
Ah yes, this should keep the lot of us discussing potential error handling routines and procedures for a while.
Paul.
