End - All resources freed automatically?

[forumuser]

Hi,

sorry, I'm new to programming. Found PureBasic, looked at the help file, the forum, thought: Not too hard to read (the source code), helpful people around. Bought it...

My first naïve question:
Does: "End" terminate a program in such a way, that everything that was setup before like:

Code: Select all

BindEvent()
AddKeyboardShortcut()
AllocateMemory()
etc.

is freed automatically or is an exit procedure necessary, that needs to clean everything up before proceeding with "End"?

[walbus]

PB give all free automatically

[forumuser]

So as long as I handle these two like so:

Code: Select all

    ; Memory
    *mem = AllocateMemory(<some size>)

    If *mem
      ; Do something
      FreeMemory(*mem)
    EndIf

    Global Dim Temp(10)
    ; Assign some value to it
    If ArraySize(Temp()) <> -1
      FreeArray(Temp())
    EndIf

I'm fine and don't have to worry about anything else?

[Marc56us]

Help

Code: Select all

Syntax
    End [ExitCode]
Description
    Ends the program execution correctly.

Unless I'm mistaken, all resources (keyboard shortkeys, memory allocation etc) created by your program are released automatically (as in any other language)

It does not matter where the "End" instruction is (even in a procedure)

"Global" Keyword does not mean operating system variable.

[Dude]

Global Dim and AllocateMemory you must give free again

Global is used for your app variables; nothing more. When your app ends, the variables are gone (freed).

For AllocateMemory, the manual says: "[...] allocated memory blocks are automatically freed when the program ends."

So yes, "End" will clean both of these up.

Special note for threads: Threads can keep running even after "End" is executed and your exe no longer shows in the Task Manager. So, always end your threads correctly before "End". It's happened to me and I don't know what I did or how, but it can happen.

[Bisonte]

For AllocateMemory, the manual says: "[...] allocated memory blocks are automatically freed when the program ends."

With one exception: Memory that is allocated with or by WindowsAPI (I think this also applies to the other OS API).

[Fred]

Windows automatically release memory as well. Threads are also closed on program end. To sum up: all is released automatically when program end, no need to do manual cleanup

[forumuser]

Thanks for all the answers, appreciate it!

[TI-994A]

It should also be noted that the End command is only required if the program needs to be explicitly terminated while an event loop is still running.

Simply breaking the active event loop would also essentially terminate the program and trigger all associated housekeeping tasks.

Code: Select all

OpenWindow(0, 100, 100, 250, 100, "Program Termination")
While WaitWindowEvent() <> #PB_Event_CloseWindow : Wend

;the program safely ends here when the While/Wend loop is broken

It's technically a super Break.