PureBasic Forums - English

Hi,

Here's a simple skeleton window program. (I'm trying out Microsoft window style codes rather than the rather verbose PB constants).
Question is, would the END statement handle closing any active timers, sounds and images - or should they be closed explicitly in a shutdown routine ?

best wishes,

Graham

The end statement doesn't do anything really.
When a program ends, the operating system takes care of releasing any resources, so you don't need
to worry about memory leaks or something like that. However, there are some native WinAPI functions that need to be handled carfully.
But as long as you're using PB only functions or the vast majority of WinAPI functions, you won't run into any problems.

It's still good practice though to clean everything up yourself.
That way you can also keep track of memory leaks or other unwanted behaviour during runtime,
for example if you allocate more memory than you free at the end.

It's still good practice though to clean everything up yourself.

Thanks Shield .. I'll do that then.

all the best,

Graham

At the end of Program, the most is freed by windows (for example Memory) and the rest by PB, for example PB closes all opened
Files. But this doesn't require the "End" command, only the end of program.

The use of End in a program is not required but is included in the keywords as a matter of completeness with other BASIC keywords.


A handy use of End is to use it in conjunction with EnableExplicit at the top of your source. Place End first, then EnableExplicit. Then compile your code. It will check the source for declared variables and procedures but won't run any of it. Don't forget to remove End after your done checking the variable and procedure names.

Demivec wrote:Place End first, then EnableExplicit. Then compile your code. It will check the source for declared variables and procedures but won't run any of it.

Now how did you come up with that one
Nice tip Demivec.

skywalk wrote:

Demivec wrote:Place End first, then EnableExplicit. Then compile your code. It will check the source for declared variables and procedures but won't run any of it.

Now how did you come up with that one
Nice tip Demivec.

I didn't invent it but unfortunately can't determine who suggested it first in the forum.

Shield wrote:The end statement doesn't do anything really.
When a program ends, the operating system takes care of releasing any resources, so you don't need
to worry about memory leaks or something like that. However, there are some native WinAPI functions that need to be handled carfully.
But as long as you're using PB only functions or the vast majority of WinAPI functions, you won't run into any problems.

It's still good practice though to clean everything up yourself.
That way you can also keep track of memory leaks or other unwanted behaviour during runtime,
for example if you allocate more memory than you free at the end.

Actually PB takes care of all that, and a lot of stuff is done on end, so you can forget about manual cleanup.

Yeah, I'm sure PB does clean up properly as it should, but it probably doesn't make any difference
if you use End or ExitProcess_()...or does it?

Wellcome to the party, GWS, its nice to see that you are here too.

I'll do my best to help you, and so will everyone else over here.

Hey, another old, new, old programmer. (reference to another thread where it was saying everyone was old on the forum) Interesting that you want to work in Hex.

Welcome to the party. The joy of discovery every day.. at least it is for me.

Shield wrote:Yeah, I'm sure PB does clean up properly as it should, but it probably doesn't make any difference
if you use End or ExitProcess_()...or does it?

I didn't seen this answer, but you should really use 'End' as ExitProcess_() will exits immediately without calling PB cleanup routines.

Demivec wrote:Place End first, then EnableExplicit. Then compile your code. It will check the source for declared variables and procedures but won't run any of it.

As i remember the changelog, PB5.10 comes with the possibility
to just compile everything without running the created program.
So you don't have to write that "end"

The "end" Command is usefull because you can stop execution
whereever it is needed.

PMV wrote:

Demivec wrote:Place End first, then EnableExplicit. Then compile your code. It will check the source for declared variables and procedures but won't run any of it.

As i remember the changelog, PB5.10 comes with the possibility
to just compile everything without running the created program.
So you don't have to write that "end"

The "end" Command is usefull because you can stop execution
whereever it is needed.

Yes, it's a nice addition to v5.10, however last year (when the suggestion was made) that wasn't possible.

Reassuring to know that Fred has arranged for end to clear up any mess-up my code might make!